Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
A direct command skips the review prompt. Inspect the source before running it.
No audit gaps found. Run `/kata-audit-milestone` first.
2. Prioritize Gaps
Group gaps by priority from REQUIREMENTS.md:
Priority
Action
must
Create phase, blocks milestone
should
Create phase, recommended
nice
Ask user: include or defer?
For integration/flow gaps, infer priority from affected requirements.
3. Group Gaps into Phases
Cluster related gaps into logical phases:
Grouping rules:
Same affected phase → combine into one fix phase
Same subsystem (auth, API, UI) → combine
Dependency order (fix stubs before wiring)
Keep phases focused: 2-4 tasks each
Example grouping:
Gap: DASH-01 unsatisfied (Dashboard doesn't fetch)
Gap: Integration Phase 1→3 (Auth not passed to API calls)
Gap: Flow "View dashboard" broken at data fetch
→ Phase 6: "Wire Dashboard to API"
- Add fetch to Dashboard.tsx
- Include auth header in fetch
- Handle response, update state
- Render user data
4. Determine Phase Numbers
Find highest existing phase:
# Scan all phase directories across states
ALL_PHASE_DIRS=""for state in active pending completed; do
[ -d ".planning/phases/${state}" ] && ALL_PHASE_DIRS="${ALL_PHASE_DIRS}$(find .planning/phases/${state} -maxdepth 1 -type d -not -name "${state}" 2>/dev/null)"done# Fallback: include flat directories (backward compatibility)
FLAT_DIRS=$(find .planning/phases -maxdepth 1 -type d -name "[0-9]*" 2>/dev/null)
[ -n "$FLAT_DIRS" ] && ALL_PHASE_DIRS="${ALL_PHASE_DIRS}${FLAT_DIRS}"echo"$ALL_PHASE_DIRS" | tr' ''\n' | sort -V | tail -1
New phases continue from there:
If Phase 5 is highest, gaps become Phase 6, 7, 8...
## ✓ Gap Closure Phases Created**Phases added:** {N} - {M}
**Gaps addressed:** {count} requirements, {count} integration, {count} flows
---
## ▶ Next Up**Plan first gap closure phase**`/kata-plan-phase {N}`<sub>`/clear` first → fresh context window</sub>
---
**Also available:**-`/kata-execute-phase {N}` — if plans already exist
-`cat .planning/ROADMAP.md` — see updated roadmap
---
**After all gap phases complete:**`/kata-audit-milestone` — re-audit to verify gaps closed
`/kata-complete-milestone {version}` — archive when audit passes
<gap_to_phase_mapping>
How Gaps Become Tasks
Requirement gap → Tasks:
gap:id:DASH-01description:"User sees their data"reason:"Dashboard exists but doesn't fetch from API"missing:-"useEffect with fetch to /api/user/data"-"State for user data"-"Render user data in JSX"becomes:phase:"Wire Dashboard Data"tasks:-name:"Add data fetching"files: [src/components/Dashboard.tsx]
action:"Add useEffect that fetches /api/user/data on mount"-name:"Add state management"files: [src/components/Dashboard.tsx]
action:"Add useState for userData, loading, error states"-name:"Render user data"files: [src/components/Dashboard.tsx]
action:"Replace placeholder with userData.map rendering"
Integration gap → Tasks:
gap:from_phase:1to_phase:3connection:"Auth token → API calls"reason:"Dashboard API calls don't include auth header"missing:-"Auth header in fetch calls"-"Token refresh on 401"becomes:phase:"Add Auth to Dashboard API Calls"tasks:-name:"Add auth header to fetches"files: [src/components/Dashboard.tsx, src/lib/api.ts]
action:"Include Authorization header with token in all API calls"-name:"Handle 401 responses"files: [src/lib/api.ts]
action:"Add interceptor to refresh token or redirect to login on 401"
Flow gap → Tasks:
gap:name:"User views dashboard after login"broken_at:"Dashboard data load"reason:"No fetch call"missing:-"Fetch user data on mount"-"Display loading state"-"Render user data"becomes:# Usually same phase as requirement/integration gap# Flow gaps often overlap with other gap types
</gap_to_phase_mapping>
<success_criteria>
MILESTONE-AUDIT.md loaded and gaps parsed
Gaps prioritized (must/should/nice)
Gaps grouped into logical phases
User confirmed phase plan
ROADMAP.md updated with new phases
Phase directories created
Changes committed
User knows to run /kata-plan-phase next
</success_criteria>
