kiro-spec-batch

Orchestrate dependency-ordered waves to generate spec artifacts for roadmap features.

1|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/taku-o/gitignore-merge --skill kiro-spec-batch-taku-o
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kiro-spec-batch
Source: https://github.com/taku-o/gitignore-merge/tree/main/.claude/skills/kiro-spec-batch
Command: npx skills add https://github.com/taku-o/gitignore-merge --skill kiro-spec-batch-taku-o

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinating the creation of complete feature specs by aligning multiple artifacts across a roadmap, reducing manual coordination and ensuring consistency.

Core Features & Use Cases

  • Dependency-aware planning and wave-based execution for roadmap features
  • Parallel subagent orchestration to generate spec.json, requirements.md, design.md, and tasks.md
  • Roadmap validation, cross-spec consistency checks, and auditable revisions
  • Lightweight governance: changes staged in roadmap and reviewed after batch completion

Quick Start

Initiate the dependency-aware spec batch workflow to generate all pending specs.

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 in parallel across a multi-feature roadmap?

Dependency-ordered spec batch generation organizes end-to-end artifact creation by orchestrating waves for roadmap features. It produces spec.json, requirements.md, design.md, and tasks.md in a consistent, auditable sequence.

How does dependency-aware planning work for spec batch generation?

Dependency-aware planning sequences roadmap features into execution waves based on their dependencies. It applies strict stepwise execution and validation checks while auto-approving generated specs.

Can I use this workflow to automate requirements.md and design.md creation for multiple features?

Yes, parallel subagent orchestration automates requirements.md and design.md creation. The workflow generates all required spec artifacts for multiple features simultaneously while maintaining consistency.

What's the best way to ensure cross-spec consistency when generating multiple feature specs?

Use a batch workflow with built-in validation checks and roadmap validation to ensure cross-spec consistency. Cross-spec review remains a separate governance step after batch completion.

Does this spec batch process automatically update the roadmap?

No, the spec batch process stages changes in the roadmap but leaves updates as a separate governance step. Roadmap changes are reviewed after batch completion.

When should I avoid using wave-based spec orchestration for roadmap features?

Avoid wave-based spec orchestration if your project lacks a multi-feature roadmap or requires manual cross-spec review during generation. The workflow is designed for parallel, auto-approved spec artifacts.