kiro-spec-batch

1# Spec Batch
2 
3<background_information>
4- **Success Criteria**:
5  - All features have complete spec files (spec.json, requirements.md, design.md, tasks.md)
6  - Dependency ordering respected (upstream specs complete before downstream)
7  - Independent features processed in parallel via sub-agent dispatch
8  - Cross-spec consistency verified (data models, interfaces, naming)
9  - Mixed roadmap context understood without breaking `## Specs (dependency order)` parsing
10  - Controller context stays lightweight (sub-agents do the heavy work)
11</background_information>
12 
13<instructions>
14 
15## Step 1: Read Roadmap and Validate
16 
171. Read `{{KIRO_DIR}}/steering/roadmap.md`
182. Parse the `## Specs (dependency order)` section to extract:
19   - Feature names
20   - One-line descriptions
21   - Dependencies for each feature
22   - Completion status (`[x]` = done, `[ ]` = pending)
233. If present, also read for context:
24   - `## Existing Spec Updates`
25   - `## Direct Implementation Candidates`
26   Do not include these in dependency-wave execution; they are awareness-only inputs for sequencing and consistency review.
274. For each pending feature in `## Specs (dependency order)`, verify `{{KIRO_DIR}}/specs/<feature>/brief.md` exists
285. If any brief.md is missing, stop and report: "Missing brief.md for: [list]. Run `/kiro-discovery` to generate briefs first."
29 
30## Step 2: Build Dependency Waves
31 
32Group pending features into waves based on dependencies:
33…