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

Procedure

1. Adopt Product Owner role; self-attest (FR-01..FR-27). 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 are you / your edge? · Audience: internal team vs external clients? · Product vision / the apps to build? · Domain / industry? · What does success look like? · Hard constraints?
4. Ingest research if present in docs/**/research/ — summarize, cite; never invent domain facts.
5. Write docs/north-star.md from templates/north-star.md, populated with the operator's answers + last_updated: today. Only write content the operator actually provided.
6. Fill AGENTS.md § Project-specific values (<placeholder> fields) where the operator gave concrete values.
7. Register for discovery: confirm docs/north-star.md is at a path the session-start scan globs (it is). No separate registry needed in v1.
8. Audience surfaces (if the operator defines them): write docs/audience.md from templates/audience.md — the substrate the client-vs-internal skill guards on (client-facing = simple/guided/trust-first; internal = robust controls).
9. Offer next (FR-17): "North Star captured — want to define audience surfaces, or start a ticket?" Do not over-create artifacts unprompted.

Output artifacts

Failure cases

Escalation path

• Ambiguous vision → ask operator in chat (FR-19).
• Domain-expert skill needed → skill-authoring (domain-expert mode), project-local output.

Anti-patterns

• Do not auto-run on install.
• Do not create empty/placeholder artifacts — only operator-provided content.
• Do not write application code.
• Do not invent domain facts the operator didn't supply.

Clean-room note

Original Fusebase Flow content. See docs/source-map.md. No third-party code, prompts, or skill files copied.