Follow meaningful improvements to how Blueprint helps you plan, build, review, and ship. Routine fixes and internal refactors stay out of the feed.
Latest changes
Product history that matters.
Each entry focuses on what changed for developers using the workflow, with direct links into the relevant documentation.
Shared local and GitHub verification
Blueprint now gives local agent work and GitHub Actions one project-specific Verify command through the optional `/ci` setup.
The CI skill detects the real stack, package manager, default branch, configured checks, and existing workflows before it proposes a change.
Verify combines only checks the project already has, ordered as typecheck, tests, then build, so local work and GitHub run the same recipe.
Existing CI is preserved, and setup stops before push, remote rulesets, git hooks, coverage, browser tests, security scans, or version matrices.
The testing, implementation, completion, Autopilot, Doctor, onboarding, and adoption workflows now share clear verification responsibilities.
The findings ledger
Audit findings now live in a durable, file-backed ledger, and serious ones block the merge until a review confirms the repair.
Every audit finding gets a durable ID, severity, and status in blueprint/context/findings.md, so review results survive a context clear instead of vanishing with the chat.
Completion refuses to merge while a P0 or P1 finding is open or fixed. A repair clears only through a fresh review, your explicit accepted decision with a recorded reason, or an evidence-backed invalid verdict.
Resolved findings archive with the feature or fix they belong to, and existing projects pick this up with a normal npx create-ai-blueprint update.
Safe completed-feature rollbacks
Completed features can now be reversed through the same reviewed, file-backed workflow used to build them.
Rollback matches a checked build-plan item to its archived spec and exact git commit before proposing any product change.
Later commits are reviewed for dependency risk, while plans, context, adapters, and history are excluded from the reverse patch.
Completion preserves the original feature archive, adds a separate rollback record, and unchecks the roadmap item without rewriting git history.
Safer in-place Blueprint updates
Existing projects can now preview and apply Blueprint workflow updates without overwriting their plans, context, or history.
Dry-run mode shows which managed files would be added, updated, removed, or treated as conflicts before anything changes.
Manifest hashes protect locally modified workflow files, while project-owned plans, context, history, and agent instructions stay outside the updater's ownership boundary.
Conflicting managed files can be backed up and replaced after confirmation, and older installations can establish a safe update baseline.
Stronger quality gates for audit and autopilot
Audit and autopilot now use clearer quality checks while keeping fixes and final approval in your hands.
Audit reports maintainability, duplication, dead code, and missing test coverage without editing the project.
Autopilot includes a targeted quality pass while remaining an explicit opt-in workflow.
Both commands preserve the review gates before completion, merge, or push.
Worked examples for writing project plans
A new guide shows how to turn a rough product idea into useful project and build plans before running overview.
Includes complete project-plan and build-plan examples for a small habit tracker.
Shows the right level of detail for planning without writing a full specification too early.
Connects the planning documents directly to the overview and feature workflow.
A standalone home and documentation system
AI Blueprint gained a dedicated website that explains the workflow, durable files, commands, and setup paths in one place.
Separates the fresh-project and existing-codebase setup paths.
Documents the complete feature loop from specification through verification and completion.
Adds content-driven command, file, quality, adapter, and troubleshooting guides.
Release readiness for Render and Vercel
The release command can prepare a project for Render or Vercel while keeping deployment and remote changes behind explicit approval.
Detects the project stack and recommends a suitable supported platform.
Creates or updates local release configuration and documents required environment variables.
Verifies local readiness without silently deploying, pushing, or changing remote services.
A manual review path with try
The try command turns the current or most recently completed feature into a focused walkthrough a person can follow.
Explains what to start, where to go, what to click, and what to expect.
Uses the active feature spec or archived history instead of inventing a generic test path.
Keeps agent-side verification and human review as separate, useful checks.
Codex support and a clearer setup workflow
AI Blueprint added a Codex adapter plus guided onboarding, health checks, and a stronger plan normalization step.
Adds project-local Codex skills alongside the Claude Code adapter.
Onboard detects the real stack and records the commands future agents should use.
Doctor checks the installation, while overview validates the plans before feature work begins.