kiro-spec-quick

To generate software specifications automatically, provide a short project description and use the --auto flag to fully automate all phases. The pipeline initializes the spec directory and produces requirements, design, and task lists without requiring step-by-step manual approval.

Scaffolding a feature spec produces spec.json, requirements.md, design.md, and tasks.md files. The process initializes a structured spec directory using project templates to provide a consistent starting point for feature-driven agentic SDLC workflows.

Yes, you can run spec generation step-by-step with user approval by using the interactive mode. This mode guides you through the four-phase pipeline, allowing you to review and approve the initialization, requirements, design, and task generation phases individually.

Yes, the spec generation pipeline enforces uniqueness checks for feature names to ensure safe template-driven generation. It also includes error handling and recovery suggestions to maintain consistency across the initialized spec files.

The best way to scaffold a complete spec skeleton for a new feature is to invoke the generator with a short description like "user profile with avatar upload." The pipeline immediately produces the requirements, design, and task breakdowns ready for implementation.

The final sanity review in the generation pipeline validates the produced requirements, design, and task lists after all four phases complete. It ensures the generated spec.json and markdown files are consistent and ready for feature-driven agentic SDLC workflows.