kiro-spec-batch

Generate specification files for pending roadmap features in dependency waves.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill orchestrates end-to-end specification creation for multiple roadmap features, removing the manual coordination burden of sequencing, parallelization, and cross-spec consistency checks so teams can produce complete specs reliably and quickly.

Core Features & Use Cases

  • Dependency-aware batching: Parses the ## Specs (dependency order) section of .kiro/steering/roadmap.md and groups pending features into strict execution waves so upstream work completes before downstream work begins.
  • Parallel subagent dispatch: Launches parallel Agent subagents per wave to generate spec.json, requirements.md, design.md, and tasks.md for each feature while keeping the controller context lightweight.
  • Verification and review gates: Verifies produced artifacts, runs a cross-spec consistency review, and optionally dispatches remediation subagents for fixes, enforcing approvals and safety constraints.
  • Use Case: Ideal for product teams preparing a coordinated rollout of multiple interdependent features where specs must be produced, validated, and kept consistent across services and data models.

Quick Start

Run the kiro-spec-batch skill to generate complete specs for all pending features listed in .kiro/steering/roadmap.md.

Frequently Asked Questions about kiro-spec-batch

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

FAQPage Schema
How do I generate feature specs for an entire roadmap with dependencies?

To generate feature specs for a dependency-ordered roadmap, you need a tool that parses roadmap sections and creates requirements, designs, and task lists. This skill reads your roadmap file, groups pending features into execution waves, and produces complete spec files for each feature.

What is dependency-ordered spec generation and how does it work?

Dependency-ordered spec generation is the process of creating specification files by strictly sequencing features into execution waves. It works by parsing your roadmap, grouping upstream features first, and launching parallel subagents to generate spec.json, requirements.md, design.md, and tasks.md per feature.

How do I automate batch creation of requirements, design, and task files for multiple features?

Automating batch creation of requirements, design, and task files requires dispatching parallel subagents across dependency waves. This skill orchestrates the parallel generation of spec.json, requirements.md, design.md, and tasks.md for all pending features listed in your roadmap.

Can I use parallel subagent dispatch to produce consistent cross-spec feature specifications?

Parallel subagent dispatch can produce consistent cross-spec feature specifications when paired with verification gates. This skill launches parallel agents per dependency wave, then runs a cross-spec consistency review and optionally dispatches remediation subagents to enforce consistency.

How do I ensure upstream feature specs complete before downstream specs in a batch process?

To ensure upstream feature specs complete before downstream specs in a batch process, you must enforce strict wave ordering. This skill parses the dependency order section of your roadmap and groups features into strict execution waves, preventing downstream generation until upstream work finishes.

What file format does the roadmap need to be in for automated spec generation?

The roadmap file format needs to be a markdown file located at .kiro/steering/roadmap.md with a specific dependency order section. The skill reads this file alongside individual brief.md files in the .kiro/specs/ directory to generate the complete specification artifacts.