kiro-spec-init

Initialize KiRo spec files from a project description and templates.

Updated Apr 5, 2026

Search Tags:#templates #requirements #spec #initialization #kiro #specs

Ready to run

npx skills add https://github.com/shimaMatz/driver-copilot --skill kiro-spec-init-shimamatz

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: kiro-spec-init
Source: https://github.com/shimaMatz/driver-copilot/tree/main/.cursor/skills/kiro-spec-init
Command: npx skills add https://github.com/shimaMatz/driver-copilot --skill kiro-spec-init-shimamatz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the upfront scaffolding for KiRo specs by turning a project description into a structured spec.json and requirements.md, reducing repetitive setup and ensuring consistency.

Core Features & Use Cases

Auto-generate a unique feature name from the project description using the discovery brief when available.
Create spec.json and requirements.md in the target .kiro/specs/[feature-name]/ directory using standardized templates.
Detect naming conflicts and manage duplicates by proposing numeric suffixes.
Leverage discovery briefs (.kiro/specs/{feature-name}/brief.md) to pre-fill project descriptions and skip redundant questions.
Validate required inputs and provide clear error messages for missing templates or permissions.

Quick Start

Run the kiro-spec-requirements command for your new feature to generate its requirements.md.

Frequently Asked Questions about kiro-spec-init

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I auto-generate requirements.md and spec.json from a brief?▼

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.

How do I create a unique feature name for Kiro specs?▼

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.

Do I need existing templates to initialize Kiro spec files?▼

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.

What happens if a feature directory is missing during spec initialization?▼

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.

Can I skip clarification questions when scaffolding requirements?▼

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.

Why does spec initialization fail with a permissions error?▼

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.