When to adopt
Use adoption when the repository already contains meaningful product code, shipped behavior, or established conventions. A fresh-project worksheet cannot safely infer which behavior is intentional and which files are historical accidents.
Install the overlay
Run the installer from the root of the application repository.
cd established-app
npx create-ai-blueprint@latest
Choose the Codex adapter, Claude Code adapter, or both. The installer leaves the application’s root README intact and places workflow documentation under blueprint/.
Run the adoption survey
Run $adopt in Codex or /adopt in Claude Code. The skill reads the repository, identifies the stack and existing features, and asks about product intent that code cannot reveal.
Adoption creates or updates:
blueprint/project-plan.mdwith the product directionblueprint/build-plan.mdwith shipped features already checkedblueprint/context/coding-standards.mdwith observed conventions
Review the generated plans carefully. Adoption can describe code, but only you can confirm product intent and future priorities.
Generate the overview
After reviewing the plans, run $overview or /overview. The generated project overview becomes the compact project context agents read in future sessions.
Continue normally
The build loop is the same after adoption:
/feature -> review -> /implement -> /check -> /complete
The next feature comes from the first unchecked build-plan item. Existing features remain checked so the workflow does not try to rebuild them.