Overview

When to use it

Run $overview or /overview after the project plan and build plan contain real project decisions. The plans can be written directly, developed through any AI conversation, or created with optional Discovery. Run Overview again when those plans change materially. Do not run it before or after every feature when the plans are unchanged. Discovery is never required.

Reads

• blueprint/project-plan.md
• blueprint/build-plan.md

Writes

• blueprint/context/project-overview.md
• blueprint/build-plan.md when clear feature lists need tracking syntax, or when you approve a plan change

Initial planning baseline

On the initial pre-feature run, Overview can offer one local commit for the approved Blueprint setup, plans, and generated project context. It shows the exact candidate diff and asks before staging or committing anything. The commit uses chore: establish Blueprint project baseline and is never pushed automatically.

The offer works on the default branch or an unchanged dedicated setup branch before Feature 1. On a setup branch, the same approval creates the commit, fast-forwards it into the default branch, returns there, and deletes the setup branch locally.

Overview skips the offer for local-only Blueprint installations and after a generated overview is already committed. If the repository has no first commit, it returns to Onboard’s guided recovery instead of failing late or mixing application source into the Blueprint baseline.

Validation

Overview accepts clear bullets, numbered lists, or separated feature lines and automatically converts them to numbered checkboxes before generating context. It preserves wording, order, feature count, headings, notes, nesting, existing IDs, and completion markers. Existing valid checklists stay unchanged. New IDs avoid identities already used by the plan, active work, or history.

Formatting needs no extra approval. Adding, removing, splitting, combining, reordering, or changing the meaning of features still requires your decision. Overview asks when boundaries or IDs are ambiguous and flags vague items, oversized bundles, setup chores, and disagreements between the plans.

If the build plan is missing or still a stub, Overview proposes a checklist from the project plan and waits for approval before writing it. It never invents features or generates context while the build plan remains a placeholder.

What the generated overview adds

The overview consolidates purpose, users, features, technical direction, concrete data contracts, build order, and open questions. It remains downstream of the two plans, so edit the plans and regenerate instead of patching it by hand.

Overview keeps the generated file below 20,000 bytes. It compacts repeated narrative while preserving concrete contracts, build order, and constraints. If those distinct facts cannot fit, it stops and identifies which plan section needs to be split or moved to a focused reference.