kiro-spec-init

Generate spec.json and requirements.md from a project description using templates.

Updated Jan 26, 2026
One-click install
npx skills add https://github.com/miyamo2/braider --skill kiro-spec-init-miyamo2
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kiro-spec-init
Source: https://github.com/miyamo2/braider/tree/main/.gemini/skills/kiro-spec-init
Command: npx skills add https://github.com/miyamo2/braider --skill kiro-spec-init-miyamo2

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This SKILL simplifies and accelerates starting a new specification by deriving a unique feature name from a project description and scaffolding the spec structure with templates.

Core Features & Use Cases

  • Generate a unique feature name from the project description and initialize the specification structure.
  • Check for a brief.md in .kiro/specs/{feature-name}/brief.md and pre-fill the project description to minimize clarifications.
  • Initialize spec.json and requirements.md using templates, replacing placeholders like {{FEATURE_NAME}} and {{TIMESTAMP}} and performing validation and conflict checks.

Quick Start

Invoke kiro-spec-init to generate spec.json and requirements.md from your brief and the provided templates.

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 specification structure from a project description?

To initialize a specification structure, this Skill derives a unique feature name from your project description and scaffolds the spec directory by generating spec.json and requirements.md using guided templates.

What is the best way to scaffold spec.json and requirements.md using templates?

Scaffolding spec.json and requirements.md is done by using built-in templates that automatically replace placeholders like {{FEATURE_NAME}} and {{TIMESTAMP}} while performing validation and conflict checks during initialization.

Do I need a YAML frontmatter in SKILL.md to generate a feature specification?

Yes, generating a feature specification requires a YAML frontmatter containing name and description in SKILL.md to ensure unique naming and safely create files under the spec directory.

Can I pre-fill the project description to minimize clarifications during spec initialization?

You can pre-fill the project description during spec initialization by placing a brief.md in the .kiro/specs/{feature-name}/ directory, which the Skill searches for to automatically extract your discovery brief.

What happens if there are naming conflicts when initializing specs?

When initializing specs, naming conflicts are automatically handled by deriving a unique feature name from the project description and performing validation checks before safely creating files under the spec directory.