Files you own
| File | Purpose |
|---|---|
blueprint/config.json |
Deterministic review, verification, branch, quality-gate, and Continuous Mode policy |
blueprint/project-plan.md |
Product problem, users, MVP, data, stack, monetization, and UI direction |
blueprint/build-plan.md |
Ordered checkbox list of feature-sized outcomes |
blueprint/context/coding-standards.md |
Project conventions and testing expectations |
blueprint/context/ai-interaction.md |
Review, communication, and workflow preferences |
Generated context
| File | Generated by | Purpose |
|---|---|---|
context/project-overview.md |
/overview |
Compact project context derived from the plans |
context/current-feature.md |
/feature, /fix, or /rollback |
One active buildable scope with steps and proof |
context/findings.md |
/audit |
Findings ledger with durable IDs and statuses; open or fixed P0/P1 findings block completion |
context/review.md |
/audit independent current |
Pending handoff or completed receipt tied to the exact checkpoint, spec, reviewer selection, and evidence |
Edit upstream plans and regenerate the overview instead of patching downstream context by hand.
History
blueprint/history/features/ and blueprint/history/fixes/ store completed specs.
blueprint/history/rollbacks/ stores dated reversal records with the target
archive and commit, reason, dependency review, compatibility work, and proof. The
original feature archive remains in place, so history shows both what shipped and
why it was later removed.
Each feature build keeps its own archive: NN-name.md for the first build and
NN-name--build-2.md, --build-3.md, and so on after completed rollbacks. The
stable plan ID stays the same even if the title changes. The spec freezes the
build attempt before review, and earlier archives remain unchanged. Rollback
records name the exact build they reverse.
Tool adapters
Codex, GitHub Copilot, and Google Antigravity share project skills under
.agents/skills/. Claude Code project skills live under .claude/skills/.
OpenCode can use either tree, so it does not need duplicate skills under
.opencode/skills/. Google Antigravity does not need its own skill tree.
Projects using only one tool can remove the unused adapter after onboarding
confirms the choice.
Update metadata
| Path | Purpose |
|---|---|
blueprint/.state/manifest.json |
Installed version, selected adapters, and hashes for Blueprint-managed files |
blueprint/.state/.gitignore |
Keeps temporary staging files and local backups out of git |
blueprint/.state/run.json |
Generated record of the active or most recent substantial Blueprint command |
blueprint/.state/review-specs/ |
Exact ignored spec snapshots used by new local-only independent-review requests |
blueprint/.state/backups/ |
Pre-update copies of managed files that were replaced or removed |
The updater owns workflow skills. It does not manage project plans, generated
configuration, context, history, AGENTS.md, or CLAUDE.md. An unchanged
blueprint/README.md from an older installer is retired during update, while a
locally modified copy is reported as a conflict. See
Updating Blueprint for conflict handling and
legacy installs.
The managed Doctor skill includes the standalone activity helper used by all
tracked skills. It validates and atomically replaces run.json; users should not
edit that generated file manually.