kiro-spec-batch

1# kiro-spec-batch Skill
2 
3## Core Mission
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 subagent 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 (subagents do the heavy work)
11 
12## Execution Steps
13 
14### Step 1: Read Roadmap and Validate
15 
161. Read `{{KIRO_DIR}}/steering/roadmap.md`
172. Parse the `## Specs (dependency order)` section to extract:
18   - Feature names
19   - One-line descriptions
20   - Dependencies for each feature
21   - Completion status (`[x]` = done, `[ ]` = pending)
223. If present, also read for context:
23   - `## Existing Spec Updates`
24   - `## Direct Implementation Candidates`
25   Do not include these in dependency-wave execution; they are awareness-only inputs for sequencing and consistency review.
264. For each pending feature in `## Specs (dependency order)`, verify `{{KIRO_DIR}}/specs/<feature>/brief.md` exists
275. If any brief.md is missing, stop and report: "Missing brief.md for: [list]. Run `/kiro-discovery` to generate briefs first."
28 
29### Step 2: Build Dependency Waves
30 
31Group pending features into waves based on dependencies:
32…