kiro-spec-init

Generate a structured spec directory with template-based files from a project description.

2|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/snicmakino/kolt --skill kiro-spec-init-snicmakino
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kiro-spec-init
Source: https://github.com/snicmakino/kolt/tree/main/.claude/skills/kiro-spec-init
Command: npx skills add https://github.com/snicmakino/kolt --skill kiro-spec-init-snicmakino

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts a plain project description into a structured spec scaffold, reducing manual setup and ensuring a consistent starting point for specs.

Core Features & Use Cases

  • Generates a feature-based spec scaffold from a concise project description.
  • Initializes spec.json and requirements.md using templates, timestamps, and localization.
  • Validates uniqueness to avoid conflicts and supports template-driven customization.

Quick Start

Supply a project description to generate a full spec scaffold.

Frequently Asked Questions about kiro-spec-init

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

FAQPage Schema
How do I generate a structured specification scaffold from a plain project description?

To generate a structured specification scaffold, provide a concise project description to transform it into a spec directory initialized with template-based files like spec.json and requirements.md.

What is the best way to automate spec directory initialization and avoid naming conflicts?

Automating spec directory initialization uses a guided workflow that validates uniqueness to avoid conflicts before creating the directory and initializing files from templates.

Do I need a specific template configuration to initialize spec.json and requirements.md?

Yes, initializing spec.json and requirements.md requires access to the .kiro settings templates and a writable filesystem to generate the scaffold with timestamps and localization.

Can I customize the generated files when scaffolding a feature-based spec?

Yes, the generated spec scaffold supports template-driven customization, allowing you to adapt the initialized requirements.md and spec.json files for your feature-based spec.

Why does generating a spec scaffold require a writable filesystem?

Generating a spec scaffold requires a writable filesystem because the process physically creates a spec directory and saves the initialized template files directly onto your local storage.

Does scaffolding specs from templates work without manual file setup?

Scaffolding specs from templates eliminates manual file setup by automatically generating a structured spec directory with initialized files from a concise project description.