kiro-spec-batch

Generating feature specifications from a roadmap involves grouping features into dependency waves and dispatching parallel subagents per wave to create requirements, design, and task decomposition files while respecting ordering constraints.

Dependency-wave orchestration groups pending roadmap features into waves based on declared dependencies and dispatches parallel subagents per wave to generate specifications, ensuring correct execution order without manual coordination.

Cross-spec consistency is enforced by a dedicated reviewer that detects and remediates data model, interface, naming, and boundary mismatches across all generated specifications, surfacing integration issues before implementation begins.

You can automatically create requirements.md, design.md, tasks.md, and spec.json for roadmap features by invoking phase-specific skills that auto-approve where indicated, provided each feature has a brief.md context file.

Yes, a brief.md context file is required for each roadmap feature, as the parallel subagent pipeline reads this context to initialize and execute the per-feature spec phases including requirements, design, and task decomposition.

Limitations include the strict requirement for brief.md context files for each feature and rigid dependency-wave ordering, meaning missing context or unresolved dependencies in earlier waves will block downstream spec generation and cross-spec review.