advancelisted

# Advance Phase Thin wrapper around the `sdlc_advance_phase` MCP tool so operators can move phases without hand-assembling tool-call arguments. Paired with `/vibeflow:flow-status` for inspection. ## Usage ``` /vibeflow:advance [TARGET_PHASE] [humanOverrideNote="..."] ``` Arguments: - `TARGET_PHASE` (optional since v2.5.2): one of `REQUIREMENTS`, `DESIGN`, `ARCHITECTURE`, `PLANNING`, `DEVELOPMENT`, `TESTING`, `DEPLOYMENT`. Case-insensitive. **When omitted**, the skill defaults to the next phase in the canonical SDLC sequence based on `currentPhase` (see "Phase order" below). - `humanOverrideNote="<reason>"` (optional): operator-supplied justification when advancing under a HUMAN_APPROVAL_REQUIRED consensus verdict (Sprint 17-C). The note is written to the `phase_advanced` event payload and surfaced on subsequent SessionStart calls by `load-sdlc-context.sh`. Examples: ``` /vibeflow:advance # → next phase from currentPhase /vibeflow:advance DESIGN /vibeflow:advance DESIGN humanOverrideNote="YÖS tier resolved offline with Legal" /vibeflow:advance design # case-insensitive; uppercased for you ``` ### Phase order (canonical) ``` REQUIREMENTS → DESIGN → ARCHITECTURE → PLANNING → DEVELOPMENT → TESTING → DEPLOYMENT ``` If `currentPhase == DEPLOYMENT`, no default next phase exists — the skill stops with "Already at the last phase; nothing to advance. Use `/vibeflow:flow-status` to in