kiro-spec-init

Initialize a unique spec directory with template-generated spec.json and requirements.md files.

1.5k|242|Updated Feb 16, 2017
One-click install
npx skills add https://github.com/growilabs/growi --skill kiro-spec-init-growilabs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kiro-spec-init
Source: https://github.com/growilabs/growi/tree/main/.claude/skills/kiro-spec-init
Command: npx skills add https://github.com/growilabs/growi --skill kiro-spec-init-growilabs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Streamlines the creation of a standardized specification directory from a project description, enabling consistent scoping and requirements capture.

Core Features & Use Cases

  • Generate a new spec directory under .kiro/specs/[feature-name]/ with spec.json and requirements.md
  • Read brief.md if present to prefill fields and avoid redundant prompts
  • Ensure unique naming and automatic conflict resolution
  • Initialize files using templates and sensible defaults

Quick Start

Provide a project description to generate and initialize the specification skeleton.

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

To generate requirements from a project description, provide your text to initialize a new spec directory. The skill creates a structured folder containing spec.json and requirements.md using built-in templates.

How do I create a spec directory using a brief?

Create a spec directory by placing a brief.md file at .kiro/specs/{feature-name}/. The skill reads this brief to prefill the project description and checks for naming conflicts before generating the files.

What is the best way to initialize project specifications automatically?

The best way to initialize project specifications is by using template-driven generation. Provide a project description to automatically create a standardized skeleton with spec.json and requirements.md under .kiro/specs.

Can I use my own templates for spec initialization?

Spec initialization relies on templates located at .kiro/settings/templates/specs. You can customize these template files to ensure your generated spec.json and requirements.md match your project's specific requirements.

Does the spec initialization process support multiple languages?

Yes, the spec initialization process includes automatic language detection. It analyzes your provided project description or brief.md content to generate the spec.json and requirements.md files in the matching language.

What happens if a spec name conflict occurs during initialization?

When a spec name conflict occurs during initialization, the skill performs automatic conflict resolution. It checks the existing .kiro/specs directory structure before proceeding to ensure unique naming for your new spec directory.