kiro-spec-batch

Orchestrates automated spec generation for roadmap features via dependency waves.

Updated Apr 5, 2026

Search Tags:#roadmap #orchestration #dependency-management #quality-review #parallel-dispatch #spec-batch

Ready to run

npx skills add https://github.com/shimaMatz/driver-copilot --skill kiro-spec-batch-shimamatz

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: kiro-spec-batch
Source: https://github.com/shimaMatz/driver-copilot/tree/main/.cursor/skills/kiro-spec-batch
Command: npx skills add https://github.com/shimaMatz/driver-copilot --skill kiro-spec-batch-shimamatz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Spec Batch skill orchestrates automated spec generation for roadmap features by coordinating sub-agents and enforcing dependency waves.

Core Features & Use Cases

Enforces dependency-based waves to ensure upstream specs are completed before downstream ones.
Dispatches independent features in parallel within the same wave to accelerate spec creation.
Reads roadmap.md and briefs, generates spec artifacts (spec.json, requirements.md, design.md, tasks.md) and updates progress.
Performs cross-spec consistency checks and flags issues for remediation.

Quick Start

Run the kiro discovery to identify roadmap and briefs and then trigger the kiro-spec-batch workflow to start the batch.

Frequently Asked Questions about kiro-spec-batch

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

FAQPage Schema

How do I automate spec generation for multiple roadmap features at once?▼

Automated spec generation for roadmap features is orchestrated by reading roadmap.md and briefs, then spawning phase-specific sub-agents to produce spec.json, requirements.md, design.md, and tasks.md files while updating progress upon completion.

How does dependency management work when generating specs in parallel?▼

Dependency management for parallel spec generation works by enforcing strict dependency waves, ensuring upstream specs are fully completed before downstream ones begin, while independent features dispatch in parallel within the same wave to accelerate creation.

What is the best way to maintain cross-spec consistency during batch generation?▼

Maintaining cross-spec consistency during batch generation is handled by performing automated consistency checks across all generated artifacts and flagging identified issues for remediation.

Can I use roadmap-driven spec generation without manually defining feature dependencies?▼

Roadmap-driven spec generation requires explicit dependency ordering defined in the roadmap to enforce waves. Without it, the orchestrator cannot sequence upstream and downstream specs or safely parallelize independent features.

What artifacts are produced when coordinating parallel spec batches?▼

Coordinating parallel spec batches produces complete feature artifacts including spec.json, requirements.md, design.md, and tasks.md, generated by dispatching phase-specific pipelines for each feature.

Do I need to run a discovery step before triggering batch spec generation?▼

A discovery step is required to identify the roadmap and briefs before triggering the batch workflow, ensuring the orchestrator has the necessary inputs to map dependencies and spawn sub-agents correctly.