vibe-to-prodlisted

# Vibe-to-Production Pipeline Transitions a vibe-coded Python project to production quality through 6 phases, each dispatched as BOI specs. ## Usage ``` /vibe-to-prod <project-path> [--phase N] [--output-dir PATH] ``` - `<project-path>` — Absolute path to the Python source directory (required) - `--phase N` — Run only phase N (1-6). Default: start from phase 1 or resume from last completed phase. - `--output-dir PATH` — Where to write assessment outputs. Default: `projects/<project-name>-v2p/` ## Phase Overview | Phase | Name | BOI Spec | Input | Output | |-------|------|----------|-------|--------| | 1 | Assessment | `assess-<project>.spec.md` | Source code | Metrics JSON, priority list | | 2 | Safety Net | `characterize-<project>.spec.md` | P1-P2 modules from Phase 1 | Characterization tests | | 3 | Prioritization | Inline (no BOI) | Phase 1 metrics | Prioritized backlog | | 4 | Execution | `refactor-<module>.spec.md` (one per P1/P2 module) | Char tests + priority list | Refactored code | | 5 | Verification | `verify-<project>.spec.md` | Before/after metrics | Improvement report | | 6 | Maintain | Inline (no BOI) | Verification report | CI config, CLAUDE.md updates | ## Orchestration Flow ### When invoked: 1. **Validate inputs:** - Confirm `<project-path>` exists and contains `.py` files - Set `OUTPUT_DIR` (default: `$HEX_DIR/projects/<project-name>-v2p/`) - Set `PROJECT_NAME` from directory basename 2. **Check pipeline state:** - Read `$OUTPUT_DIR/pip