5d-plan
Convert expanded thinking into a concrete, multi-perspective plan. Use when: (1) After SPAR phase in 5D-SDD workflow, (2) User is ready to define what will be built, (3) User asks to 'write up the plan' or 'document what we're building,' (4) Transitioning from exploration to commitment. This phase creates the authoritative description of intent before technical specification.
What this skill does
# PLAN Phase Crystallize sparring outcomes into a concrete plan. ## Plan Structure ### 1. Problem Statement One paragraph. What problem does this solve? For whom? Why now? Avoid: Solution-focused framing. This section is about the problem, not the answer. ### 2. Proposed Solution Describe what will exist that doesn't exist now. Use plain language—no technical jargon yet. Include: - Core functionality (what it does) - Key behaviors (how it works from user perspective) - Boundaries (what it explicitly won't do) ### 3. Assumptions & Bets Make implicit assumptions explicit: ``` We assume: - [assumption about users] - [assumption about technical feasibility] - [assumption about business value] We are betting that: - [bet 1 - what we're gambling on] - [bet 2] Identity attachment risk: - [what we might be defending rather than evaluating] ``` ### 4. Thinking Level Declaration (Depth) Acknowledge current thinking level: - Are we at Level 2 (dogmatic—"this is the right way")? - Can we articulate why alternative approaches might be valid (Level 3)? - What novel insight does this plan contain (Level 4)? ### 5. Skill Dependencies (Height) Document what capabilities the plan requires: - What skills must the team have or acquire? - What domain knowledge unlocks implementation? - What's blocking progress that's outside this plan's scope? ### 6. Alternatives Considered Document what was rejected and why: | Alternative | Why Rejected | |-------------|--------------| | [option A] | [reason] | | [option B] | [reason] | This prevents re-litigating decisions later. ### 7. Quadrant Coverage Ensure plan addresses all four: | Quadrant | Plan Element | |----------|--------------| | Individual Outer | What artifacts will be created | | Individual Inner | What understanding/skills are required | | Collective Outer | How this fits existing systems | | Collective Inner | What alignment is needed across stakeholders | ### 8. Time Horizons - **V1 (this iteration):** [scope] - **V2 (next iteration):** [deferred scope] - **Explicitly not planned:** [out of scope] ## Output Format Produce a standalone document titled `PLAN.md` with the sections above. Keep it under 500 words. Plans that require more are actually multiple plans. ## Exit Criteria Proceed to REFINE when: - All sections are complete - User confirms plan matches their intent - No major gaps in quadrant coverage
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.