onboard

name

onboard

description

Set up the Blueprint after overlaying it onto a freshly scaffolded or early project. Detects the stack, relocates the copied Blueprint README when needed, updates AGENTS.md commands, sets the CLAUDE.md project title when present, tunes coding-standards.md, checks ai-interaction.md and .gitignore, asks whether Blueprint workflow files should be committed or kept local-only, confirms which tool adapters to keep, and tells the user exactly what to fill in before /overview or $overview. Use when the user runs /onboard, invokes $onboard, just copied the Blueprint into a new project, or asks what to do after overlaying the Blueprint. For an existing app with meaningful shipped features, use adopt instead.

onboard - finish the Blueprint overlay setup

Where this sits in the workflow:

scaffold app  ->  overlay Blueprint  ->  [onboard]  ->  project-plan + build-plan  ->  /overview
(user/tool)       (copied files)          (tune setup)   (user-owned inputs)       (generated context)

/onboard is the fresh-project on-ramp. It assumes the app was scaffolded first and the Blueprint files were overlaid after. Run it before filling in plans or running /overview. Its job is to make the Blueprint fit the real project before planning starts: commands, project title, conventions, ignore rules, and tool adapters. It also asks whether the Blueprint workflow files should be committed with the repo or kept local-only through .gitignore.

Use /adopt instead when the app is brownfield: real routes, shipped features, and project behavior already exist and need to be reflected into the plans.

Input

No argument is required. If the user provides context about the stack, hosting, database, auth, or preferred tool, use it as a hint and verify against files.

Step 0 - confirm this is onboarding, not adoption

Inspect the repository and the two planning docs:

• If blueprint/project-plan.md and are mostly empty or worksheet-like, proceed.