Spec mapping.
Your AI hands you a flowchart, a spec, a wall of bullet points. Then what? Spec mapping turns that into a structured plan you can build from — and that an agent can build with — instead of a diagram that dead-ends in a drawing tool.
Every AI can draw a diagram now. Then it dead-ends.
Ask any model for a flowchart and you get one in seconds. Paste it into Lucid or Miro and… it's a picture. Pretty, static, un-buildable. To turn it into an actual plan, you redraw it by hand — re-typing every box as a real task, guessing at sequence and scope.
Generation got easy. Structuring is still manual. That gap is the whole job.
Paste it, or let your agent build it.
- Paste the Mermaid. Your AI already speaks Mermaid — that's the diagram format it emits natively. Drop it into CardBoard and the board builds itself.
- Have Claude build it. Point an agent at CardBoard over MCP and it creates the map directly — reading the board's rules, proposing cards a human accepts.
Either way, it doesn't land as a loose pile of boxes. It restructures into a map that knows its own shape — because structure is built into the board, not bolted on after. That's the part Lucid and Miro can't do, and it's why the theory of maps matters: the target shape is known, so the import becomes a real plan instead of a sketch.
A plan you can build from — and build with.
Because it's a real map, you can do real work on it: slice it into releases, prioritize top to bottom, push it straight to your tracker. None of that is possible on a flat diagram.
And because it's typed, an agent can read it and propose the next cards without drifting — it knows what the board allows, so it builds the right thing instead of confidently building the wrong one.
What spec-driven development has been reaching for.
Spec-driven development got one thing exactly right: the spec is the source of truth, and the code is downstream of it. Agents drift when there's no structured spec to hold them. A spec map is that source of truth — except you can see it.
One plan, drawn for people and typed for machines.
One job, three people doing it.
It's the same loop — turn an ambiguous idea into a structured plan a second party can build from without it drifting. The only thing that changes is who that second party is.
- The business analyst — turning stakeholder conversations into a plan engineering will actually sign off on.
- The product manager — structuring an AI's output into a real plan instead of staring at a blank prompt.
- The solo founder — turning a chat with their agent into something the agent can then build.
A spec map is a story map.
The plan you land on isn't a new invention — it's a user story map, the method teams have trusted for years. Spec mapping is just the AI-era on-ramp to it: start from a chat, a spec, or a flowchart instead of a wall of sticky notes, and arrive at the same buildable plan.