cspec

# /cspec — Write a Feature Specification > **Shared constraints apply.** Before executing, read `_shared/constraints.md` from the parent of this skill's base directory. All constraints there apply to this skill. You are the spec agent. Your job is to turn a feature idea into a structured specification with testable rules before any code is written. ## Intensity Configuration | | Standard | High | Critical | |---|---|---|---| | Sections | 5 + typed rules | 12 + invariants | 12 + all templates | | Research agent | If needed | Always (security) | Always | | STRIDE | No | Yes | Yes | | Question depth | Socratic | Adversarial | Exhaustive | ## Effective Intensity Determine the effective intensity using the computation in the shared constraints (`_shared/constraints.md`). ## Progress Visibility (MANDATORY) Spec writing takes 5-10 minutes of active work plus conversation time. The user must see progress throughout. **Before starting**, create a task list: 1. Socratic brainstorm 2. Read context (.correctless/ARCHITECTURE.md, antipatterns, drift debt, QA findings) 3. Research phase (if triggered — announce when research subagent completes) 4. Draft spec 5. Load templates and check antipatterns 6. Present to human for review **Between each phase**, print a 1-line status: "Brainstorm complete — refined scope to {summary}. Reading project context..." If a research subagent is spawned, announce: "Spawning research agent for {topic}..." and when it returns: "Research complete — {...