kiro-spec-init

Generate spec.json and requirements.md from KiRo templates.

Updated Feb 25, 2024
One-click install
npx skills add https://github.com/ryowatanabe/iidx-dp-unofficial-difficulty-scraper --skill kiro-spec-init-ryowatanabe
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kiro-spec-init
Source: https://github.com/ryowatanabe/iidx-dp-unofficial-difficulty-scraper/tree/main/.claude/skills/kiro-spec-init
Command: npx skills add https://github.com/ryowatanabe/iidx-dp-unofficial-difficulty-scraper --skill kiro-spec-init-ryowatanabe

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates creating a standardized KiRo specification scaffold by generating spec.json and requirements.md from templates, saving time and reducing setup errors.

Core Features & Use Cases

  • Generate spec.json and requirements.md using centralized templates.
  • Pre-fill project description using discovery brief when available to minimize clarifying questions.
  • Validate uniqueness and handle existing directories to avoid conflicts.

Quick Start

Provide a project description and run the kiro-spec-init tool to generate a ready-to-edit 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 create a standardized project specification scaffold in markdown and json?

To create a project specification scaffold, this tool generates standardized spec.json and requirements.md files from centralized templates, ensuring a consistent structure while reducing manual setup errors and saving time.

Can I pre-fill the project description when initializing a spec to avoid answering unnecessary questions?

Yes, spec initialization can automatically pre-fill the project description by using the brief.md discovery content when available, allowing it to skip unnecessary clarifying questions during the scaffold generation process.

How does generating a new spec handle existing directories or naming conflicts?

When generating a new spec, the tool validates uniqueness and handles existing directories gracefully by surfacing any directory conflicts for user resolution rather than overwriting existing project files.

What is the best way to bootstrap a KiRo specification without manual setup errors?

The best way to bootstrap a KiRo specification is to provide a project description and run the initialization tool, which automatically generates a ready-to-edit spec scaffold using validated templates.

Do I need to manually create spec.json and requirements.md files for my project management workflow?

No, you do not need to manually create spec.json and requirements.md files; the initialization tool automatically generates both from centralized templates to standardize your project management workflow.