kiro-spec-batch

Generates complete specs for all roadmap features via parallel sub-agent dispatch by dependency wave.

Updated Jun 23, 2026
One-click install
npx skills add https://github.com/j5ik2o/marp-ai-base --skill kiro-spec-batch-j5ik2o
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kiro-spec-batch
Source: https://github.com/j5ik2o/marp-ai-base/tree/main/.agents/skills/kiro-spec-batch
Command: npx skills add https://github.com/j5ik2o/marp-ai-base --skill kiro-spec-batch-j5ik2o

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Creating specifications for every feature in a project roadmap one at a time is slow and error-prone, and specs written in isolation often conflict with each other. This Skill automates batch spec generation while enforcing dependency ordering and cross-spec consistency. ## Core Features & Use Cases - Dependency Wave Planning: Parses the roadmap's ## Specs (dependency order) section and groups pending features into waves so upstream specs complete before downstream ones start. - Parallel Sub-Agent Dispatch: Spawns sub-agents to run the full spec pipeline (init, requirements, design, tasks) for each feature in a wave, keeping the controller context lightweight. - Cross-Spec Consistency Review: Runs a dedicated review sub-agent that checks data models, interfaces, naming, task boundaries, and architecture seams across all generated specs, with up to three remediation rounds. - Use Case: After running discovery to produce a roadmap with six features, invoke this Skill to generate spec.json, requirements.md, design.md, and tasks.md for all of them in four dependency waves, then get a consistency report before implementation. ## Quick Start Ask the AI to run the spec batch skill to generate complete specs for every pending feature 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 specs for all features in a roadmap at once?

Run the spec batch workflow, which parses the roadmap's dependency-ordered specs section, groups pending features into waves, and dispatches parallel sub-agents to create spec.json, requirements.md, design.md, and tasks.md for each feature.

How does dependency wave ordering work for spec generation?

Features with no pending dependencies form Wave 1, and each subsequent wave contains features whose dependencies are all in earlier waves or already complete. A wave never starts until all features in the previous wave finish.

What happens if a brief.md file is missing for a feature?

The batch stops before execution and reports which features are missing briefs. You must run the discovery workflow first to generate the missing brief.md files before batching specs.

Does the batch process check consistency across multiple specs?

Yes. After all waves complete, a review sub-agent reads every generated spec and checks data model consistency, interface alignment, duplicate functionality, naming conventions, and task boundary overlaps, with up to three fix-and-recheck rounds.

What happens when a sub-agent fails during a wave?

The error is logged, the failed feature is skipped, and the remaining features in the wave still complete. The summary lists failures and suggests running the single-feature spec command manually for each one.

Can the batch handle circular dependencies in the roadmap?

No. If the dependency graph contains a cycle, the process stops and reports the cycle. You must fix the dependency ordering in roadmap.md before rerunning the batch.