spec-create

Generating a technical specification from a PRD involves reading the requirements, leveraging existing context files, triaging open questions, and producing implementation documentation including decision logs and ADRs at a stable docs path.

A well-structured tech spec captures the results of a collaborative design discussion, detailing component design, data models, API shapes, and implementation decisions at docs/features/{feature}/tech-spec.md.

Revising an existing tech spec when PRDs or requirements change involves tracing the modifications using ADRs and generating migration notes to maintain accurate implementation documentation.

A PRD is required before starting technical design documentation, as the workflow reads from docs/features/{feature}/prd.md to guide the design discussion and determine implementation details.

The design discussion triage process works by leveraging a sub-agent to manage questions, utilizing CONTEXT.md when present, and producing a decision log to capture implementation details in the tech spec.

A limitation of generating implementation documentation from PRDs is that the workflow enforces reading the PRD at docs/features/{feature}/prd.md, meaning it cannot proceed if the PRD file is missing.