spec

To turn handoff notes into structured design specs, provide a handoff.md entry and the system selects an appropriate template, guiding decision-making to produce a ready-to-implement spec file with context and acceptance criteria.

Documenting design decisions and requirements during a project handoff works best by transforming handoff entries into standardized spec documents, ensuring open decisions are noted and alignment is achieved across teams before implementation begins.

Generate spec documents with acceptance criteria from a handoff entry by confirming the spec workflow, which applies a step-based process to produce a timestamped file under docs/specs containing intent, context, and actionable acceptance criteria.

Yes, the spec generation workflow selects from spec templates stored under docs/specs/templates, matching the appropriate template to your handoff context to ensure the resulting documentation follows standardized formatting.

Yes, you can use this spec workflow for both design and implementation planning, as it handles a range of handoff entries and applies a guided, step-based process to produce structured documentation for alignment and execution.

The spec generation process requires user confirmation to enforce a collaborative, step-based decision-making workflow, ensuring open decisions are explicitly noted and the final spec document accurately reflects team alignment before implementation.