HomeUpdatesGitHub
Docs/Reference/File Reference

File Reference

Understand which Blueprint files you own, which are generated, and how state moves through the workflow.

Referencereferencefilescontext

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

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.

Tool adapters

Codex and GitHub Copilot 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/. 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/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.

Documentation

Search AI Blueprint

Start typing to search the documentation.