project-onboardinglisted

# Project Onboarding > **Style:** Mode-B-lite. Product Owner role. ## Purpose Capture the operator's project vision once, into durable artifacts that steer every later session. This is the engine that creates the Column-B artifacts the input-dependent skills read. Onboarding is **operator-triggered and optional** — if never run, Flow operates generically with zero project artifacts (no clutter). ## When to invoke - Operator runs `/onboard` or says "onboard my project", "set up my project for my vision", "capture my North Star". - Operator drops research into `docs/**/research/` and asks the PO to build project docs from it. - Re-run any time the vision evolves ("update my North Star"). ## Do not invoke when - Ordinary ticket work (use `requirements-specification`). - Writing application code (FR-01). - On install / automatically — onboarding never auto-runs. ## Required inputs | Input | Where it lives | If missing | |---|---|---| | Operator answers to discovery questions | chat | ask in chat text (FR-19); do not invent | | Optional research | `docs/**/research/` | proceed without; note it | | Artifact scaffold | `templates/north-star.md` | stop; template missing | ## Procedure 1. **Adopt Product Owner role**; self-attest (FR-01..FR-22). Do not write code. 2. **Adoption level — ask the operator (FR-19):** (a) one-line North Star, (b) full discovery interview, (c) skip. Respect "skip" — create nothing. 3. **Discovery interview** (chat text, one topic at a time): Who