kirospec-basic

To create local specs, run the spec-init process to generate a SPEC skeleton within your project. It validates the SPEC_NAME and initializes the .kiro/specs directory using a local script, ensuring design.md, requirements.md, and tasks.md exist without external folder dependencies.

In-project SPEC scaffolding centralizes specification creation inside your repository. You need it when you want portable specifications that rely on local rules rather than external folders, ensuring your design.md, requirements.md, and tasks.md files remain consistent and self-contained.

You initialize a new SPEC skeleton by running the spec-init process, which executes the local scripts/spec-init.sh file. This action validates your SPEC_NAME input and scaffolds the required directory structure along with the design, requirements, and tasks markdown files.

No, you do not need external folder dependencies to maintain requirements and tasks docs. This approach leverages local SPEC rules to enable portable specifications entirely within your project, verifying that the required markdown files exist locally.

The best way to ensure these docs exist consistently is using template-driven SPEC scaffolding. It reuses canonical templates for design, requirements, and tasks during initialization, automatically verifying the presence of all three required markdown files.

The spec-init process fails because SPEC_NAME validation is a required step before creating the local skeleton. Ensuring a valid SPEC_NAME allows the local script to correctly generate the specification directory and verify the required design, requirements, and tasks files.