dev-docs
Create strategic plan and dev docs. Use when starting large multi-session tasks.
What this skill does
# Dev docs system Creates a structured documentation system for large tasks to maintain context across sessions. ## When to invoke - When starting a large, multi-session task - When you need to track progress across context compactions - When working on complex implementations requiring documentation - Before major refactoring or feature development ## Usage ``` /dev-docs [task-name] ``` ## Instructions When this command runs: 1. **Create dev docs directory structure**: ``` dev/active/[task-name]/ ├── plan.md # Strategic implementation plan ├── context.md # Key files, decisions, dependencies └── tasks.md # Detailed task checklist ``` 2. **Generate plan.md** with: - Task overview and objectives - High-level implementation strategy - Key architectural decisions - Risk assessment and mitigation - Success criteria 3. **Generate context.md** with: - List of key files to modify - Important code patterns and conventions discovered - External dependencies and their versions - Design decisions and rationale - Links to relevant documentation 4. **Generate tasks.md** with: - Detailed, actionable task checklist - Estimated complexity for each task - Dependencies between tasks - Progress tracking checkboxes 5. **Update TodoWrite** with the initial tasks ## Template structure ### plan.md ```markdown # [Task Name] - Implementation plan ## Overview [Brief description of what we're building] ## Objectives - [ ] Objective 1 - [ ] Objective 2 ## Strategy [High-level approach] ## Architecture decisions - Decision 1: [rationale] ## Risks | Risk | Mitigation | | ---- | ---------- | | | | ## Success criteria - [ ] Criteria 1 ``` ### context.md ```markdown # [Task Name] - Context ## Key files - `path/to/file.ts` - [purpose] ## Code patterns - Pattern 1: [description] ## Dependencies - package@version - [why needed] ## Decisions log | Date | Decision | Rationale | | ---- | -------- | --------- | | | | | ``` ### tasks.md ```markdown # [Task Name] - Tasks ## Phase 1: Setup - [ ] Task 1 (S) - [ ] Task 2 (M) ## Phase 2: Implementation - [ ] Task 3 (L) ## Phase 3: Testing - [ ] Task 4 (S) Legend: (S)mall, (M)edium, (L)arge ``` ## Notes - Run `/update-dev-docs` before session compaction to capture progress - Keep context.md updated as you discover new information - Check off tasks in tasks.md as you complete them
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.