kiro-spec-init

Initialize .kiro/specs entries with spec.json and requirements.md from templates.

Updated Apr 17, 2026
One-click install
npx skills add https://github.com/BarryYin/Hermes-sdd --skill kiro-spec-init-barryyin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kiro-spec-init
Source: https://github.com/BarryYin/Hermes-sdd/tree/main/skills/kiro-spec-init
Command: npx skills add https://github.com/BarryYin/Hermes-sdd --skill kiro-spec-init-barryyin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the initial setup of a feature specification so engineers and product managers can reliably create consistent spec directories and baseline requirement documents without manual file and template manipulation.

Core Features & Use Cases

  • Template-driven Initialization: Reads repository templates and generates spec.json and requirements.md with placeholders replaced.
  • Brief-aware Setup: Detects and reuses discovery brief.md to prefill project description and skip redundant questions.
  • Conflict & Error Handling: Checks for naming collisions, appends suffixes if needed, and reports missing templates or write failures.
  • Use Case: Quickly initialize a new .kiro/specs entry for a discovered feature before proceeding to requirements and design steps.

Quick Start

Initialize a new specification for the feature name you provide, using any existing .kiro/specs/<feature>/brief.md and the repository templates to create spec.json and 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 create structured specification files from a project brief?

Template-driven initialization reads repository templates and any existing brief.md to automatically generate spec.json and requirements.md with placeholders replaced for your project specification.

What is the best way to initialize a .kiro/specs directory for spec-driven development?

Bootstrapping a .kiro/specs directory involves reading repository templates from .kiro/settings/templates/specs to populate baseline spec.json and requirements.md files for feature implementation.

Does spec initialization require a brief.md file to exist before running?

Spec initialization does not require a pre-existing brief.md. The process detects and reuses brief.md to prefill project descriptions if available, but proceeds with standard template population if absent.

How are naming conflicts handled when creating new feature specifications?

Naming conflicts during feature specification creation are resolved by performing uniqueness checks and automatically appending suffixes to the new spec directory name if collisions are detected.

What happens if template files are missing during requirements.md generation?

When template files are missing during requirements.md generation, the initialization process halts and reports the specific missing template or write errors back to the user.

Can I use kiro-spec-init to set up requirements for Hermes Agent projects?

kiro-spec-init is applicable to spec-driven development in Hermes Agent projects for initializing .kiro/specs entries, preparing requirements.md, and bootstrapping spec.json for feature implementation.