planning
Use when exploring has locked CONTEXT.md and the work needs planning before validation.
What this skill does
# Planning Skill Planning turns locked `CONTEXT.md` decisions into the smallest believable path to execution. Tough work uses capability/risk epics and a current story for feasibility validation. If `.khuym/onboarding.json` is missing or stale, stop and invoke `khuym:using-khuym`. ## Hard Gates - `CONTEXT.md` is source of truth. - Read critical patterns before discovery. - Run `node .codex/khuym_status.mjs --json` when available. - Use gkg first for supported ready repos; document fallback. - Start with a mode gate. - Use the least workflow that protects the work. - For tough plans, prefer `Epic Map -> Current Story Pack` over forced 2-4 phases. - Stop after the work shape/epic map until approval. - Create beads only after validation accepts feasibility, except already-proven direct/small work. - Handoff only to `khuym:validating`. ## Shape `Mode -> Shape -> Epic Map? -> Current Story Pack -> Beads`. Phase = optional milestone; epic = capability/risk area; story = end-to-end outcome; bead = worker task for validated work. Load `references/planning-reference.md` for quality rules and artifact templates. ## Flow 1. **Bootstrap:** scout, read `CONTEXT.md`, read learnings. 2. **Discovery:** map repo reality, patterns, constraints, and research. 3. **Mode gate:** choose direct, spike, small, standard, or high-risk mode. 4. **Synthesis:** write `approach.md` with path, risks, proof needs, files, and validating questions. 5. **Shape:** write direct/spike/small shape, phase plan, or epic map; present approval and stop. 6. **Prep:** after approval, write only current story/work artifacts; beads wait for feasibility unless already proven. 7. **State:** set next action to `khuym:validating`. ## Approval Gate ```text Planning has chosen the smallest work shape. Approve it before current story/work prep. Tough work uses an epic map; beads wait until feasibility passes. ``` ## Red Flags - skipping learnings or `CONTEXT.md` - skipping the mode gate - defaulting to 2-4 phases without proving the work needs phases - using phases when epics better express capability/risk areas - prep/beads before approval - future-story or future-epic beads - pseudo-beads in Markdown - vague exit states or missing dependencies - risky assumptions without a spike or validating question
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.