kiro-spec-init

To generate requirements.md and spec.json from a brief, run the initialization command to read .kiro/specs/{feature-name}/brief.md, pre-fill the description, and scaffold the structured files using standardized templates.

Creating a unique feature name for Kiro specs involves analyzing the project description and checking .kiro/specs/ for naming conflicts, proposing numeric suffixes to manage duplicates automatically.

You need existing templates located in .kiro/settings/templates/specs/ to initialize Kiro spec files, as the process validates these required inputs and provides clear error messages if they are missing.

If a feature directory is missing during spec initialization, the process automatically creates the target .kiro/specs/[feature-name]/ directory to ensure the spec.json and requirements.md files generate successfully.

You can skip clarification questions when scaffolding requirements if a discovery brief exists at .kiro/specs/{feature-name}/brief.md, which is read to pre-fill the project description automatically.

Spec initialization fails with a permissions error when the process lacks the required file system permissions to create the feature directory or write the generated spec.json and requirements.md files.