kiro-spec-init

Initialize structured project specifications from briefs into .kiro/specs directories.

1|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/taku-o/gitignore-merge --skill kiro-spec-init-taku-o
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kiro-spec-init
Source: https://github.com/taku-o/gitignore-merge/tree/main/.claude/skills/kiro-spec-init
Command: npx skills add https://github.com/taku-o/gitignore-merge --skill kiro-spec-init-taku-o

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates creating a consistent specification directory and initial files from a short project description or discovery brief, removing manual setup, naming conflicts, and template lookup friction so teams can move faster from discovery to planning.

Core Features & Use Cases

  • Feature name generation: derive a unique, filesystem-safe feature-name from the project description and resolve naming conflicts automatically.
  • Template-driven initialization: read templates from .kiro/settings/templates/specs and generate spec.json and requirements.md with placeholders replaced and timestamp and language detection applied.
  • Brief-aware clarification: read .kiro/specs/{feature}/brief.md when present to pre-fill project description or interactively ask clarifying questions to ensure who/what/why are specified.
  • Use case: a product manager converting discovery output into a standardized spec directory without manual file editing.

Quick Start

Initialize a new specification from the project description "social sign-in for mobile app".

Frequently Asked Questions about kiro-spec-init

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

FAQPage Schema
How do I initialize a project specification from a brief description?

To initialize a project specification, this tool reads a project description, generates a unique filesystem-safe feature-name, and creates a structured spec directory containing spec.json and requirements.md files using predefined templates.

How does specification template initialization handle placeholders and timestamps?

Specification template initialization works by reading templates from the .kiro/settings/templates/specs directory, replacing placeholders with project-specific data, and applying automatic language detection and timestamps to the generated requirements.md and spec.json files.

Can I use a discovery brief to pre-fill the requirements.md project description?

Yes, you can use a discovery brief. The tool reads brief.md from the feature directory to pre-fill the project description, and it interactively prompts for clarifying questions to ensure who, what, and why are specified.

What is the best way to automate feature-name generation for specification directories?

Automating feature-name generation is handled by deriving a unique, filesystem-safe name directly from the project description, resolving any naming conflicts automatically to prevent duplicate spec directories.

Do I need .kiro/settings/templates/specs to create spec.json and requirements.md?

Yes, you need .kiro/settings/templates/specs. The tool validates the presence of these templates before initializing the structured specification directory and generating the required spec.json and requirements.md files.

Why does specification initialization prompt for clarification during project setup?

Specification initialization prompts for clarification when the brief description lacks sufficient detail, ensuring the generated requirements.md explicitly defines the who, what, and why of the project before scaffolding completes.