8.2 — The readiness checklist
On this page
8.2 — The readiness checklist
"Ready to hand off" isn't a single switch — it's a handful of things that all need to be true before you point a coding agent at the project. The app surfaces each one where it lives:
- The Prepare page shows a green "Ready to build" banner once the blueprint is generated, nothing is pending review, and coverage is clear.
- The Development page's three tabs — Plan, Hand off, Track — each carry a small status dot that turns green as that step completes.
- The Hand off tab is the connection surface: an API-key card and the MCP config card for your project.
What to check
| Check | Where | Counts as "done" when |
|---|---|---|
| Blueprint generated | Prepare page | A Prepare-for-Dev run completed — all four pipelines (interactions, state machines, permissions, data contracts) are green. Failed pipelines can be retried without losing completed work. |
| Flagged items resolved | Prepare page | The amber "Flagged items" banner is gone. Anything a pipeline couldn't auto-resolve is approved or corrected in the Review dialog. |
| Coverage clear | Prepare page | No open coverage gaps. Together with the two above, this is exactly what the green "Ready to build" banner asserts. |
| Sprints planned | Development → Plan tab | At least one sprint exists. Note: this resets if you delete all sprints. |
| API key for your coding agent | Development → Hand off tab | You have at least one personal access token under your account. The card shows your key count and links to Account → Developer. |
| MCP server configured in your IDE | Development → Hand off tab | Informational only — the card gives you the config to paste, but we can't see your IDE's settings file. Once configured (Claude Desktop's 🔨 icon, Cursor's MCP servers list, etc.) you're good. |
The first five checks are verifiable — they have hard truth in the database, and the banners and tab dots reflect them live. The last is a reminder that the configuration step exists.
Why we don't verify the IDE config
The MCP config file lives in your IDE's settings directory (e.g. ~/Library/Application Support/Claude/claude_desktop_config.json for Claude Desktop on macOS). VibeMap is a cloud app — it can't read your local filesystem. So we surface the step prominently on the Hand off tab and let you self-verify by either:
- Looking for the IDE's visual confirmation (🔨 icon, MCP server list, etc.).
- Asking your agent "List my VibeMap projects" and seeing them returned.
- Watching the Activity feed below the kanban on the Track tab — once your agent makes its first call, you'll see "Agent vm_xxxxx claimed XYZ" appear.
The real signal that everything works is your agent successfully calling a VibeMap MCP tool and a card moving on the kanban.
Before the blueprint exists
The Hand off tab intentionally holds back the connection details until a Prepare-for-Dev run has completed — you'll see an empty state pointing you to the Prepare page instead. There's no point wiring up an agent before it has a blueprint to build from.