phase-v2

name	phase_v2
description	Run an entire development phase hands-off. Uses a bash wrapper script that invokes /epic_v2 per slice with fresh context. Usage - /phase_v2 <phase-number> [starting-slice]

Phase Orchestration v2

Run all remaining slices in a development phase completely hands-off. Each slice gets its own fresh claude invocation via an external bash loop — keeping each context well under the 1M ceiling, even for L-effort slices with large test suites and CodeRabbit iteration.

How It Works

The orchestration is done by scripts/run-phase.sh, a bash script that:

1. Reads the phase task file (tasks/phase{N}-*.md)
2. Extracts the ordered slice list from the Implementation Order / Slices tables (rows starting with | **NNNX** |)
3. Skips slices already marked **Done**
4. For each remaining slice, invokes:

   claude -p "/epic_v2 {SLICE} auto-merge" --dangerously-skip-permissions --model opus
   

   The /epic_v2 skill natively supports slice IDs (digits+letter → single-slice mode).
5. After each invocation, checks if that slice was marked Done in the task file
6. If Done → next slice. If not Done → stops (you investigate and restart)

Each claude invocation gets a fresh context window. No cross-slice context accumulation; no epic-level prompt-overflow failures.

Usage

# Run all remaining slices in phase 10
./scripts/run-phase.sh 10

# Start from a specific slice (skips earlier ones even if not Done)
./scripts/run-phase.sh 10 84A

# Start from the first slice of an epic (e.g., 84 → starts at 84A)
./scripts/run-phase.sh 10 84


./scripts/run-phase.sh 10 --dry-run