workflow-mastery
# Workflow Mastery Skill
What this skill does
# Workflow Mastery Skill ## Overview This skill provides Claude with expert knowledge of the Claude Ultra workflow system, enabling automatic application of best practices for software development, task management, and context preservation. ## When to Activate Activate this skill when: - Starting a new development session - Working on complex multi-step tasks - Managing git operations - Performing code reviews - Debugging issues - Working with subagents ## Workflow Protocol ### Phase 1: UNDERSTAND 1. Parse the request - what is actually being asked? 2. Check constraints - tech stack, patterns, existing code 3. Run `git status` to understand current state 4. Load relevant context ### Phase 2: PLAN 1. For complex tasks, use Plan Mode 2. Use @explore agent to research unfamiliar code BEFORE modifying 3. Break work into atomic tasks 4. Get confirmation before major changes ### Phase 3: EXECUTE 1. Delegate to specialized subagents for distinct subtasks 2. Use @task-worker agents in parallel for independent file operations 3. Keep commits atomic - one logical change per commit 4. Run tests/typecheck after each significant change ### Phase 4: VERIFY 1. Run the thing (tests, build, typecheck) 2. Show output as evidence 3. Review git diff before committing 4. Never claim "done" without proof ## Agent Selection Guide | Task | Agent | When | |------|-------|------| | Codebase search | @explore | Before modifying unfamiliar code | | File modifications | @task-worker | Parallel independent changes | | Code review | @code-reviewer | Before any PR | | Bug investigation | @debugger | Root cause analysis | | Security check | @security-auditor | Auth/data changes | | Architecture | @architect | System design decisions | ## Autonomy Modes - **Autonomous**: Execute end-to-end with minimal check-ins - **Collaborative** (default): Check in at major decision points - **Supervised**: Explain each step before executing ## Context Preservation - Main agent handles orchestration - Subagents handle detailed work - This keeps main context clean for longer sessions - Use memory-bank for persistent knowledge ## Quality Gates Before completing any task: - Run the thing (tests, build, command) - Show the output as evidence - Verify it actually works
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.