kiro-spec-batch

Generate spec.json, requirements.md, design.md, and tasks.md for roadmap features.

Updated Jan 26, 2026
One-click install
npx skills add https://github.com/miyamo2/braider --skill kiro-spec-batch-miyamo2
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kiro-spec-batch
Source: https://github.com/miyamo2/braider/tree/main/.gemini/skills/kiro-spec-batch
Command: npx skills add https://github.com/miyamo2/braider --skill kiro-spec-batch-miyamo2

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create a scalable coordination layer to generate complete specs (requirements, design, tasks) for all features listed in roadmap.md by orchestrating parallel sub-agents in dependency-order waves.

Core Features & Use Cases

  • Orchestrates multi-feature spec generation across roadmap-driven projects in parallel where possible.
  • Enforces dependency-order waves to ensure upstream specs are ready before downstream tasks.
  • Produces spec.json, requirements.md, design.md, and tasks.md for each feature, enabling downstream development.

Quick Start

Run the kiro-spec-batch workflow to trigger batch spec generation across the roadmap features.

Frequently Asked Questions about kiro-spec-batch

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

FAQPage Schema
How do I batch-create specs for multiple roadmap features at once?

Batch-create specs for multiple roadmap features by orchestrating parallel sub-agents in dependency-order waves. This generates complete specification artifacts, including requirements, design, and tasks, across all listed features simultaneously.

What is dependency-wave orchestration for spec generation?

Dependency-wave orchestration ensures upstream specifications are fully generated before downstream tasks begin. It coordinates parallel sub-agents to enforce dependency order, preventing blockers during multi-feature roadmap spec creation.

How do I ensure cross-spec consistency when generating multiple feature specs?

Ensure cross-spec consistency by running automated consistency checks after parallel spec generation. This validates that all generated requirements, design, and tasks artifacts align across the entire roadmap.

Can I automatically approve generated specs in a roadmap-driven workflow?

Yes, you can automatically approve generated specs during batch creation. The workflow auto-approves specs produced by parallel sub-agents to streamline multi-feature roadmap orchestration.

Do I need a roadmap.md file to generate feature specs in parallel?

Yes, a roadmap.md file is required to identify features and their dependencies. The batch spec generation workflow reads this roadmap to coordinate parallel sub-agents and produce spec.json, requirements.md, design.md, and tasks.md.

What's the best way to generate design and tasks documents for a project roadmap?

Generate design and tasks documents for a project roadmap by running a batch spec creation workflow that orchestrates parallel sub-agents. This produces consistent design.md and tasks.md files while respecting feature dependency order.