kiro-spec-quick

Feature specification generation uses a four-phase pipeline to scaffold templates, produce requirements, create designs, and output actionable tasks directly from a brief project description or discovery brief.

Yes, automatic mode executes the end-to-end spec pipeline without manual drafting, generating requirements.md, design.md, and tasks.md files while providing progress reporting and a final sanity review.

Yes, generating specs requires read and write access to repository templates and spec directories, specifically reading discovery briefs and templates from the .kiro directory to initialize the scaffolding.

Interactive mode requires step-by-step user approval throughout the pipeline, while automatic mode runs fully automated end-to-end execution with continuous progress reporting and a final sanity review.

Template-based file creation initializes spec scaffolding from repository templates, then invokes sub-skills to sequentially generate requirements, design outputs, and implementation tasks into a dedicated feature folder.

The best way to structure design outputs and tasks is using the four-phase spec pipeline, which writes structured design.md and tasks.md files alongside spec.json and requirements.md into a feature folder.