kiro-spec-batch

Automate feature spec generation by parsing roadmap.md and dispatching parallel subagents to create spec.json, requirements.md, design.md, and tasks.md for each feature. It coordinates the entire workflow by dependency order.

Dependency management enforces upstream completion before initializing downstream specs. Features without blocking dependencies run in parallel waves, ensuring prerequisite designs are validated before dependent feature specs begin generation.

Yes, you can generate requirements and design docs in parallel by grouping independent features into execution waves. Subagents are dispatched simultaneously for features with no upstream dependencies, accelerating roadmap execution.

Cross-spec consistency review is a post-generation validation pass that checks alignment across all generated feature specs. You need it during roadmap orchestration to verify that downstream requirements match upstream design decisions.

Yes, the spec generation process includes file verification and auto-approve logic to confirm that spec.json, requirements.md, design.md, and tasks.md are correctly initialized. It applies SKILL.md templates to validate each file.

Orchestrating spec generation by dependency waves requires a clearly defined roadmap.md with explicit upstream and downstream relationships. Complex circular dependencies or ambiguous feature ordering cannot be processed until the graph is resolved.