kiro-spec-batchlisted

# kiro-spec-batch Skill ## Core Mission - **Success Criteria**: - All features have complete spec files (spec.json, requirements.md, design.md, tasks.md) - Dependency ordering respected (upstream specs complete before downstream) - Independent features processed in parallel via subagent dispatch - Cross-spec consistency verified (data models, interfaces, naming) - Mixed roadmap context understood without breaking `## Specs (dependency order)` parsing - Controller context stays lightweight (subagents do the heavy work) ## Execution Steps ### Step 1: Read Roadmap and Validate 1. Read `.kiro/steering/roadmap.md` 2. Parse the `## Specs (dependency order)` section to extract: - Feature names - One-line descriptions - Dependencies for each feature - Completion status (`[x]` = done, `[ ]` = pending) 3. If present, also read for context: - `## Existing Spec Updates` - `## Direct Implementation Candidates` Do not include these in dependency-wave execution; they are awareness-only inputs for sequencing and consistency review. 4. For each pending feature in `## Specs (dependency order)`, verify `.kiro/specs/<feature>/brief.md` exists 5. If any brief.md is missing, stop and report: "Missing brief.md for: [list]. Run `/kiro-discovery` to generate briefs first." ### Step 2: Build Dependency Waves Group pending features into waves based on dependencies: - **Wave 1**: Features with no dependencies (or all dependencies already completed `[x]`) - **Wave