plan-builder
Write implementation plans with appropriate templates based on complexity. Use when planning features or changes. Provides minimal, standard, and full templates for different scope levels.
What this skill does
# Plan Builder Write implementation plans using the appropriate template based on complexity. ## Template Selection | Complexity | When to Use | Template | |------------|-------------|----------| | **Minimal** | Simple bugs, small improvements, clear single-file changes | `references/minimal.md` | | **Standard** | Most features, complex bugs, team collaboration | `references/standard.md` | | **Comprehensive** | Major features, architectural changes, multi-phase work | `references/comprehensive.md` | ## Selection Criteria ### Use Minimal When - Fix is obvious and localized - Single file or 2-3 related files - No architectural decisions needed - Clear acceptance criteria from description ### Use Standard When (Default) - Multiple components affected - Requires research or external docs - Team needs context for review - Has dependencies or risks ### Use Comprehensive When - New system or major feature - Multiple phases of work - Architectural decisions required - Cross-cutting concerns (security, performance) - Involves multiple teams or stakeholders ## Plan Output Write plans to: `docs/plans/[YYYYMMDDHHMMSS]_<title>.md` Include in every plan: - Research findings with file paths (e.g., `src/models/user.rb:42`) - External documentation URLs - Related issues/PRs if known - **Acceptance Criteria** from user input (populated from blueprint Step 2) ## Conditional Sections ### UI Features Include "Design System Reference" section when feature involves: - Pages, components, forms, buttons, modals - Visual design elements ### DevOps Features Include "Infrastructure Context" section when feature involves: - Terraform/OpenTofu, Ansible, cloud resources - Docker, CI/CD, infrastructure ## Anti-Patterns | Don't | Do | |-------|-----| | Use comprehensive for simple bugs | Match template to actual complexity | | Skip Acceptance Criteria | Always include testable criteria | | Leave placeholder text | Fill all sections or remove them | | Over-plan obvious changes | Minimal template exists for a reason |
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.