spec
This skill should be used when the user asks to "write a spec", "spec this out", "let's spec", "requirements gathering", "interview me about this feature", "define the requirements", or wants a structured interview-driven specification before implementation.
What this skill does
# Spec Workflow **Intention:** $ARGUMENTS ## Step 1: In-Depth Interview Interview me thoroughly using AskUserQuestion about this intention. Ask non-obvious questions covering: - Technical implementation details and architecture decisions - UI/UX considerations if applicable - Edge cases, error handling, security implications - Performance and maintainability tradeoffs - Constraints: what's out of scope, what to avoid - Existing patterns to follow, dependencies to use or avoid - Priorities if tradeoffs must be made - What could go wrong, past experiences that inform this **Interview rules:** - Ask 2-4 questions per round - Go deep on answers with follow-ups - Continue for 3-5+ rounds minimum - Use multiSelect when multiple options apply - Don't rush - extract every relevant detail ## Step 2: Write the Spec Once complete, ask where to save (suggest `.claude/specs/<slug>.md`) and write: - **Overview**: One paragraph summary - **Goals / Non-Goals**: What's in and out of scope - **Requirements**: From the interview - **Technical Approach**: Implementation strategy - **Open Questions**: Remaining uncertainties - **Acceptance Criteria**: How to know it's done ## Step 3: Next Steps Ask how to proceed with these options: 1. **Start working** - Begin implementing now 2. **Start ralph-loop** - Run `/ralph-loop` with the spec 3. **Done for now** - Just save the spec If they choose ralph-loop: 1. **CRITICAL: Always include termination conditions** - Ralph loops without termination run forever: - `--max-iterations 50` (or appropriate limit for task complexity) - `--completion-promise "SPEC_COMPLETE: <spec-filename>"` (derive from the spec file) 2. Ask about permissions: - Normal permissions flow - Skip permissions (note: requires `--dangerously-skip-permissions` flag on CLI) Example command to run: ``` /ralph-loop <spec-path> --max-iterations 50 --completion-promise "SPEC_COMPLETE: slash-commands.md" ``` When implementing, output the completion promise phrase ONLY when all acceptance criteria are genuinely complete.
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.