Most roadmaps are fiction with deadlines.
The dates on a Gantt chart are guesses dressed up as commitments. By the time the quarter starts, half the dates have slipped and nobody believes the chart anymore — so it gets updated less, then ignored, then replaced with a spreadsheet that’s also wrong by Friday.
annsa’s roadmap is what’s true now. Specs are sequenced by impact, not by date. Two rails show what you intend (Backlog, Later, Next) and what’s happening (Building, Shipped, Shared). You override the sequence when judgment beats the algorithm, and annsa remembers what it recommended so you can always reset.
Sequence, override, dispatch.
The roadmap is generated, not maintained.
Click “Sequence Roadmap” and annsa scores every spec by impact, then assigns each one a recommended bucket — Backlog, Later or Next.
Drag a card between Backlog, Later and Next. Annsa remembers what it suggested, so “Reset to recommended” appears whenever your sequence diverges from the data.
The Flow rail — Building, Shipped, Shared — fills in from spec status as specs move. PRs, branches and last activity surface on building cards.
“Hand off to Cursor” or “Hand off to Claude” dispatches the spec to your coding agent. The card carries the customer quote and the rationale through.
The roadmap that sequences itself, then defers to you.
Most roadmaps are either a Gantt nobody updates or a vote-counter that rewards the loudest customer. annsa’s roadmap is generated by impact and overridable by judgment.
“Sequence Roadmap” ranks every spec by business impact and assigns it a bucket. No dates to maintain, no Gantt to update — the order reflects the evidence.
Move a card between Horizon buckets and annsa holds both — your sequence and the data’s. “Reset to recommended” appears so you can always see what the system said and choose between them.
Each card has a dispatch button — straight to Cursor or Claude Code. The spec, the customer context and the repo context all travel with it.
Everything on the board.
Horizon (Backlog, Later, Next) is intent and the only rail you reorder. Flow (Building, Shipped, Shared) is state and updates from spec status. Both visible, neither confused for the other.
File count and layer tags — frontend, backend, e2e — inferred from the spec’s Files-to-Touch.
The line a customer sent appears on the card when the spec ships, so the why stays attached.
Why this is being built now — surfaced from the sequencing reasoning.
PR number, branch name and last activity — or time-in-state when no PR is linked yet.
Comfortable or compact. The board adapts to how much you want on screen.
Hide columns you’re not focused on. Saved per user.
From the Move dropdown — turn the spec into a GitHub issue, customer context attached.
Asked and answered.
The Sequence button scores every spec by impact — using the same evidence behind your priority list — and assigns each one a recommended bucket: Backlog, Later or Next.
Yes, any card, any time. Drag it to a different Horizon bucket or use the Move dropdown. Annsa remembers what it recommended so you can reset if you change your mind.
Because dates on roadmaps are usually guesses dressed up as commitments. The order reflects impact and reality — what’s most worth doing, what’s happening — instead of a deadline nobody can hit.
Horizon is what you intend — Backlog, Later, Next. You manage it, and it’s the rail you drag cards between. Flow is what’s happening — Building, Shipped, Shared. Annsa manages it from spec status.
It dispatches the spec to Cursor or Claude Code from the card. The agent pulls the live spec, the customer citations and your repo’s conventions, then starts work in the linked GitHub repo.
The hand-off surfaces a “GitHub repo required” message — annsa needs the repo to dispatch the agent. Connect GitHub once and hand-off works on every card.
Learn more about the annsa Delivery suite.
The full feature overview — specs, roadmap, ship and share back.
One build-ready spec from the feedback behind a priority, cited line by line.
Every shipped spec mapped onto your codebase, classified by blast radius.
Ships specs to your editor over MCP and closes the loop with the customers who asked.
When a spec ships, drafts each customer who asked a follow-up in their words.