Spec map
Every spec, mapped to your codebase.
See every shipped spec by folder, customer theme or product page — with blast radius classified before work begins.
Codebase coverage + risk
Three views. One underlying map.
Folder · theme · page · blast radius
See where work lands before you start.
Every spec becomes a navigable record of codebase coverage, customer demand and delivery risk.
Map the folders.
Group the themes.
Classify blast radius.
Delivery · Spec map
Coverage and risk, derived from the work itself.
Codebase view
Folder tree, recursively expandable. Click a node, see the specs.
Theme view
Specs grouped by the cluster theme they came from.
Page view
Specs grouped by the product page they touch, parsed from component paths.
01 · Spec
The first draft is already written.
One cited artifact: What to Build, Why It Matters, Customer Voice, Files to Touch, Done When.
02 · Roadmap
A roadmap that sequences itself.
Two rails show intention and flow; one button sequences work by impact.
03 · Spec map
Every spec, on the map of your codebase.
Codebase, theme and page views with blast-radius classification.
04 · Ship
The spec leaves Annsa as code.
Connect over MCP; hand grounded work to Cursor or Claude Code.
05 · Share Back
The customer who asked is the first to know.
Annsa drafts the follow-up in their context; you review before sending.
Learn more about the Annsa Delivery suite.
Asked + answered.
Q1
What is the spec map?
Every spec organised by where it lands in the codebase, the theme it came from or the product page it touches.
Q2
What is blast radius?
A classification of how many files and folders a spec touches: contained, moderate or cross-cutting.
Q3
How is the folder tree built?
Directly from the Files-to-Touch section in every grounded specification.