write-spec

name	write-spec
description	Generate canonical change specification
model	sonnet
allowed-tools	["Read","Write","Edit","Glob","Grep","Bash","WebFetch","mcp__*"]

Generate a COMPLETE, implementation-agnostic CHANGE SPECIFICATION from planning session context.

User invocation: /write-spec <workItemRef>

Inputs other than workItemRef MUST be sourced from the active planning context; NOTHING may be invented. Resulting spec becomes authoritative input for /write-plan.

$ARGUMENTS - `workItemRef` = first token matching pattern `-` (e.g., `PDEV-123`, `GH-456`) - If no valid `workItemRef` found, output NEEDS_INPUT: ``` NEEDS_INPUT: workItemRef required Usage: /write-spec Example: /write-spec PDEV-123 ```

<discovery_rules> Given workItemRef:

1. Search for existing folder: doc/changes/**/*--<workItemRef>--*/
2. If not found, create: doc/changes/<YYYY-MM>/<YYYY-MM-DD>--<workItemRef>--<slug>/

Files:

• Spec: chg-<workItemRef>-spec.md
• Branch: <change.type>/<workItemRef>/<slug> </discovery_rules>

1. Parse `workItemRef` from $ARGUMENTS 2. Gather planning-session context from conversation 3. Compute slug from title (lowercase kebab-case, ≤60 chars) 4. Locate or create change folder per 5. Determine `change.type` from context (feat/fix/refactor/etc.) 6. Checkout/create branch 7. Delegate to `@spec-writer` agent (it has the full template and rules) 8. Report: path to created spec, next step: `/write-plan ` After successful execution: - Created file path - Branch name - Recommendation: "Run `/write-plan ` to generate the implementation plan" - No implementation details in the spec - Only the spec file may be written - Await human approval before `/write-plan`