kiro-spec-init

To initialize a kiro specification, you provide a project description and the tool generates a structured .kiro/specs directory with template-created spec.json and requirements.md files. It embeds the current timestamp and detected language into the generated spec scaffold.

To prevent naming conflicts when creating kiro specs, the initialization process checks existing .kiro/specs paths for duplicate feature names. If a conflict is detected, it supports automatic conflict resolution to ensure a unique directory is created.

Yes, you can reuse an existing discovery brief to prefill your kiro spec. If a brief.md file is available, the tool extracts its content to prefill the project description, avoiding unnecessary clarifying questions during the spec generation process.

Kiro spec generation uses templates to create spec.json and requirements.md files while automatically detecting the project language. The detected language and current timestamp are embedded directly into the generated files for consistent documentation.

No, you do not need a discovery brief to bootstrap a kiro spec. You can directly supply a project description to generate the structured spec directory, but using an existing brief.md file allows the tool to prefill the description automatically.