kiro-spec-quick

To convert a feature idea into a structured spec from natural language, use a guided four-phase workflow that initializes templates and orchestrates requirements, design, and tasks generation. This process outputs an implementation-ready spec bundle including spec.json and related documents.

The best way to automate feature spec generation is to run the automatic mode using the --auto argument. This automates the initialization, requirements, design, and tasks phases to rapidly produce a standardized spec bundle without manual interactive prompts.

Yes, the spec generation workflow supports interactive mode for product management. It provides clear prompts and progress tracking, allowing engineering teams to actively guide the initialization, requirements gathering, and design phases instead of running fully automated.

Creating implementation-ready specs generates a standardized spec bundle under the .kiro/specs/{feature-name} directory. This bundle includes a spec.json file alongside structured requirements, design, and tasks documents to reduce ambiguity and handoff delays.

Yes, you can review the generated feature spec for completeness before finalizing it. The workflow includes an optional sanity review phase that checks the generated requirements, design, and tasks documents to ensure the final spec bundle is complete and implementation-ready.

To structure requirements and design tasks for engineering handoff, apply a four-phase workflow that parses arguments and invokes subtools for each section. This method reduces ambiguity by producing standardized requirements, design, and tasks documents from your initial feature description.