kiro-spec-init

Scaffolding a project spec creates a unique feature directory and generates spec.json and requirements.md files. It reads templates from settings/templates/specs to ensure consistent formatting and applies suffixes to enforce unique naming on conflicts.

To create a project spec you need template files located in settings/templates/specs. The skill checks for these required templates during initialization and reports missing files or write permission errors to help you troubleshoot setup issues.

Yes, the spec initialization process validates required templates and reports missing files. It surfaces write failures and permission issues during the scaffolding process, allowing you to troubleshoot environment setup problems before generating the feature directory.

Converting a brief into a formal spec uses the prefill mechanism to extract the project description from brief.md. It skips redundant clarification steps and writes the structured requirements.md file directly into the newly scaffolded feature directory.