spec-writer

Feature Specs Writer

Generate implementation-ready technical specifications based on the project's PRD and existing codebase patterns. Besides spec.md and plan.md, it produces a third artifact, contract.md — the operational contract consumed by implement-feature (which must satisfy it) and by evaluator (which validates against it).

Base docs (in this package): https://github.com/dayvisonassis/sdd-skills/blob/main/docs/Contrato_de_Feature.md (contract structure), https://github.com/dayvisonassis/sdd-skills/blob/main/docs/Como_criar_gates.md (gates), and https://github.com/dayvisonassis/sdd-skills/blob/main/docs/ARQUITETURA_DAS_SKILLS.md (full flow). Start with https://github.com/dayvisonassis/sdd-skills/blob/main/docs/GUIA_DO_WORKFLOW.md for how the skills fit together.

The skill has two modes:

• Single-feature mode (default): operates on one feature at a time, identified by its PRD feature ID (F01, F02...), with an interactive interview (Steps 1–6 below).
• Batch mode: operates on multiple features from the same wave in parallel, auto-accepting all interview recommendations. Activated automatically when the input contains multiple IDs, a wave reference, or a mix. See the Batch Mode section near the end of this file.

Output: THREE files are required:

1. spec.md - Technical specification (7 sections)
2. plan.md - Implementation plan (phases and steps)
3. contract.md - Operational contract (environment, quality gates, coverage manifest, observable criteria)

Output location: docs/<feature-id>-<kebab-name>/{spec.md,plan.md,contract.md}

• The <kebab-name> is derived from the feature's name in the PRD Section 6 (lowercase, spaces → hyphens, special characters removed). Example: F03. Video Upload → docs/F03-video-upload/.

---

Execution Steps (6 Steps)

Note: These are internal agent execution steps. The OUTPUT plan document will have 1-5 phases based on feature complexity.

Step 1: Resolve Input and Pre-Analysis