The Blueprint Preview Map

An interactive diagram of everything your spec will build and how it connects — features, roles, pages, and data as one graph. · Recommended

The bottom half of the Prepare for Dev page is the Blueprint Preview Map. It's the fastest way to sanity-check your blueprint before you hand off: if a page isn't wired to any data, or a role can't reach the pages it needs, you see it here as a missing edge instead of discovering it mid-build. The map is read-only and available on Starter and above — it's derived entirely from your existing spec with no LLM call, so viewing it never consumes generations.

Figure: Blueprint Preview Map on the Prepare page.

A confidence banner above the map keeps expectations honest: while your schema, links, or permissions are still incomplete, it labels the map as a preview of what will be built, not final code.

What's on the map

Four toggleable layers, each with its own colour:

Between them, five kinds of edges: feature groups page, role can access page, page reads/writes data, data relationships (foreign keys), and navigation between pages.

The Overview panel

A small Overview panel sits in the top-right corner of the map. It counts your nodes (roles, pages, data, links) and — below that — lists every open finding on the project, grouped by kind: Features with no user stories, Pages with UI states missing criteria, Stories with upstream changes, and so on.

Each group is a working surface, not just a count:

• Groups whose items appear on the map are clickable — click the label to highlight those nodes.
• Fix all generates the missing assets for every item in the group. Below each group, the first few items appear as chips linking to their own editor.
• Reconcile appears on the stale groups instead — those resolve through review, not regeneration. See Staleness and reconciliation.
• Auto-fix gaps, at the top of the panel, queues every fixable group at once.
• Groups with neither are marked review manually — they're judgement calls, not something a generation can close.

When the panel is empty it says so: "No findings — ready to build."

Navigating

• Layer toggles — hide layers you're not thinking about (turn off Roles while reviewing the data model).
• Search box — jump to any node by name.
• Single-feature filter — narrow the map to one feature and everything it touches.
• Layout toggle — switch between horizontal and vertical flow.
• Mini-map — orient yourself on large graphs.

The detail panel

Click any node and a detail panel opens on the right:

• Needs attention — everything outstanding on this node, each with the button that resolves it. A feature missing user stories, a page whose sections have no acceptance criteria, a broken navigation link: the panel names it, says why it matters for the build, and offers the same fix the guided review would run. Items that hold the build gate are marked Blocks build.
• Ask the agent — the speech-bubble button in the panel header opens the agent chat with this node already referenced, so you can type an instruction about it directly ("split this page in two", "write stories for this feature").
• What it is — a one-line description drawn from the spec itself.
• Coverage health — how well this node is backed by acceptance criteria.
• Connected neighbours — everything one hop away, clickable.
• Acceptance-criteria tree (pages) — the criteria that will drive this page's implementation, including the empty/error/loading UI states bound during Prepare's spec-coverage step.
• Impact preview (pages, features, roles) — see below.

Coverage lens

Toggle the Coverage lens to overlay health rings on every node: green (fully covered by acceptance criteria), amber (partial), red (no coverage). It's the visual companion to the checks that run during Prepare for Dev — a red ring here is the same gap the coverage preflight would flag.

Impact preview

For pages, features, and roles, the detail panel includes an impact preview: a deterministic walk of the foreign-key graph (no LLM) that answers "if this changes, what else is affected?" It lists the affected entities, distinguishes child records from dependent ones, and flags how hard the impact is. Use it before deciding to cut or rework something late in the spec.

Spotting what needs work

Every node card carries a count badge when something on it is outstanding — red when at least one of those items blocks the build, amber otherwise. You can read the whole map for gaps without opening anything, then click a badge's card to see and fix the list.

The badge counts the node's own gaps and its children's: a feature shows the stories missing beneath it, a page shows its sections and criteria. Nothing is hidden behind a hover.

⚡ Power-user hints

• Use it as a review checklist. Filter to one feature and walk its pages — the red badges are your to-do list before handoff, and each one carries its own fix button.
• Impact preview before you cut. Late-stage scope changes are risky; the FK walk tells you the blast radius deterministically.
• The Overview panel is the shortest path to green. Work its groups top to bottom — they're ordered blocking-first, so the items standing between you and a build-ready spec are always at the top.

↔ The traditional way

An architect draws an ERD in one tool, a sitemap in another, and a roles matrix in a third — three artefacts that drift apart the moment the spec changes. The Blueprint Preview Map is all of them as one live graph, generated from the spec, so it's always current and it shows the connections between them (which role reaches which page reads which table) that separate diagrams never capture.

What's next

• Confirm you're ready → Prepare for Dev
• Resolve the stale groups → Staleness and reconciliation
• Where the entity nodes come from → Generating schema
• Where the page nodes come from → Generating pages
• Hand off to your coding agent → Handoff overview