onboardlisted

# VibeFlow Project Onboarding ## Phase Contract This skill runs in **REQUIREMENTS** only. Before any other step, read `vibeflow.config.json`'s `currentPhase`. If it is not REQUIREMENTS, emit: > onboard is for REQUIREMENTS phase only; current is `<phase>`. If you > need to re-run onboarding, advance back or start a fresh project. …and stop. The PreToolUse `phase-write-guard` (Sprint 13) will also reject any source-code writes this skill attempts, so the only safe outputs are `vibeflow.config.json`, `.vibeflow/**`, and `docs/**`. ## Steps ### Step 0: Already onboarded? Resume, don't re-onboard (Sprint 42) **Run this first.** Onboarding is a once-per-project act. If `vibeflow.config.json` already exists, the project is initialized — do **not** re-onboard, and do **not** mis-read its existing source as "brownfield" (a greenfield project that has reached DEVELOPMENT *also* has source files; file presence is not the signal — lifecycle state is). Read `.vibeflow/state/lifecycle.json` and route: ```bash test -f vibeflow.config.json && echo EXISTS [ -f .vibeflow/state/lifecycle.json ] && jq -r '.currentCycle.status' .vibeflow/state/lifecycle.json ``` - **`currentCycle.status == "in-progress"`** → an active cycle is mid-flight. Stop and resume: > Project already onboarded (cycle `<id>`, phase `<currentPhase>`). Resuming — > nothing to re-initialize. > ▶ Next: /vibeflow:phase-runner - **`currentCycle.status == "completed"`** → the last cycle shipped; new work is a fre