phase-runnerlisted
Install: claude install-skill mytechsonamy/VibeFlow
# Phase Runner (Sprint 19-F)
The one-command phase loop. Before Sprint 19, an operator walking
REQUIREMENTS → DESIGN typed something like:
```
/vibeflow:prd-quality-analyzer docs/PRD.docx
/vibeflow:consensus-orchestrator docs/PRD.docx
/vibeflow:consensus-specialist <sid>
/vibeflow:apply-arbiter-patch <sid>
/vibeflow:consensus-orchestrator docs/PRD.docx # round 2 (manual)
/vibeflow:advance
```
Sprint 19-F collapses that to `/vibeflow:phase-runner`. Every
step uses the same artifacts + skills that were already doing the
work — phase-runner just sequences them, gates on
`phaseRunner.autoAdvance`, and bounds iteration via
`phaseRunner.maxConvergenceAttempts`.
## Usage
```
/vibeflow:phase-runner [TARGET_PHASE]
```
- `TARGET_PHASE` (optional) — REQUIREMENTS / DESIGN / ARCHITECTURE
/ PLANNING / DEVELOPMENT / TESTING / DEPLOYMENT. Default: read
`currentPhase` via `mcp__sdlc-engine__sdlc_get_state`.
Both the target phase and the current phase must match — the skill
does **not** run analyzers for a different phase than the project
is in. If they disagree the skill stops and tells the operator to
`/vibeflow:advance` first (or run the right analyzer by hand).
## Phase → analyzer map
Hardcoded in the skill. Matches `skills/phase-policy.json`
registrations + the Sprint 19-A `docs/PRIMARY-ARTIFACT.md` table.
| Phase | Analyzer skills (sequential) | Primary (resolved by marker v2) |
|---|---|---|
| REQUIREMENTS | `prd-quality-analyzer` | `<PRD path from argument or docs/>` |
|