kiro-spec-quick

Spec generation supports both automatic and interactive modes, allowing you to either fully automate the drafting process from briefs or step through spec creation manually to align teams early on software features.

The automated spec generation workflow orchestrates four phases starting from brief intake, applying local templates to produce spec.json and related docs, and concluding with a lightweight sanity review that outputs a completion summary with an optional recovery path.

Yes, local templates are required to generate the .kiro/specs/{feature-name}/ directory structure and related documents, ensuring the automated spec pipeline commands map your briefs into standardized requirements, design, and task files.

Yes, you can select interactive mode for product specification workflows, which guides you through spec generation step-by-step from briefs and discovery notes instead of running the fully automatic pipeline.

Yes, the spec pipeline performs a final lightweight sanity review after generating the specification documents, optionally using subagents to validate the output and provide a completion summary with a recovery path if needed.

Automating spec generation creates a .kiro/specs/{feature-name}/ directory containing spec.json alongside three related markdown documents: requirements.md, design.md, and tasks.md, derived from your initial briefs using local templates.