kiro-spec-init

Initialize a specification directory with spec.json and requirements.md from a project description.

Updated Jun 23, 2026
One-click install
npx skills add https://github.com/j5ik2o/marp-ai-base --skill kiro-spec-init-j5ik2o
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kiro-spec-init
Source: https://github.com/j5ik2o/marp-ai-base/tree/main/.agents/skills/kiro-spec-init
Command: npx skills add https://github.com/j5ik2o/marp-ai-base --skill kiro-spec-init-j5ik2o

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Starting a new feature specification requires consistent structure, naming, and language handling. This Skill automates the creation of the initial spec scaffolding so teams begin every feature with the same standardized files instead of hand-crafting them. ## Core Features & Use Cases - Feature Name Generation: Derives a unique feature name from the project description and resolves directory conflicts with numeric suffixes. - Template-Based Initialization: Reads templates from .kiro/settings/templates/specs/ to generate spec.json and requirements.md with placeholders replaced. - Discovery Brief Integration: Reuses an existing brief.md from a discovery session to pre-fill the project description and skip redundant clarification. - Language Detection: Selects Japanese or English requirement skeletons based on the input language, defaulting to Japanese. - Use Case: A product manager describes a new checkout feature; the Skill creates .kiro/specs/checkout-flow/ with a ready-to-fill requirements document and metadata file. ## Quick Start Initialize a new specification for a user notification feature using the project description I provide.

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 new feature specification with kiro?

Provide a project description and the Skill generates a unique feature name, creates the .kiro/specs/{feature-name}/ directory, and writes spec.json and requirements.md from templates. It does not generate requirements content, design, or tasks.

What files does spec initialization create?

It creates exactly two files: spec.json containing metadata like feature name, timestamp, and language, and requirements.md built from a language-matched skeleton template. Requirements, design, and task generation happen in later steps.

Does kiro spec init support languages other than Japanese and English?

No, only Japanese and English requirement skeletons are supported. If language detection selects an unsupported code, the Skill stops and reports the unsupported language rather than mixing template languages.

What happens if the feature name directory already exists?

If the directory exists with only a brief.md from discovery, it is reused. Otherwise a numeric suffix is appended, such as feature-name-2, and the user is notified of the automatic conflict resolution.

Why does spec initialization fail with a template missing error?

The Skill requires template files in .kiro/settings/templates/specs/, including init.json and requirements skeletons. If any are missing, it reports the specific missing path and suggests checking the repository setup.