The first draft is already written.
This is the translation layer — one artifact, drafted from the signal behind a priority. Five sections: What to Build, Why It Matters, Customer Voice, Files to Touch, Done When. Cited line by line.
Click a priority and the brief drafts itself from the underlying feedback — problem statement, jobs-to-be-done, acceptance criteria, edge cases and risks. You edit a draft instead of writing one.
Click a priority, a roadmap card, a customer record or a spec map node — the same spec opens. No promotion ritual, no two-document sync. The brief, the spec, the build are one thing.
“Sharpen the acceptance criteria.” “Add technical constraints.” “Simplify to one paragraph.” The spec updates and the previous version is kept. No re-writing from scratch.
A roadmap that sequences itself.
Two rails — what you intend (Backlog, Later, Next) and what’s happening (Building, Shipped, Shared). One button sequences the work by impact. You override when you need to; the recommendation stays so you can reset.
“Sequence Roadmap” scores every spec by impact and assigns it a recommended bucket — Backlog, Later or Next. No Gantt, no fake dates. The order reflects the evidence.
Drag a card to a different bucket and Circuit remembers the system’s suggestion. “Reset to recommended” appears whenever your sequence diverges, so you can always see what the data said.
Each card has a button — dispatch to your coding agent without leaving the roadmap. Linked PR, branch and last activity surface on the card while it’s building.
Every spec, on the map of your codebase.
Three views of the same set: by codebase folder, by theme, by product page. Each spec is classified by blast radius, so you can see at a glance what’s safe to ship and what touches everything.
A folder tree built from the Files-to-Touch section of every spec. Click a path to see the specs touching it. Click a spec to open it.
Each spec carries a blast-radius label — contained (≤ 2 files, ≤ 1 folder), moderate, or cross-cutting (≥ 5 files, ≥ 3 folders). You see what’s safe before you start.
Codebase view (folder tree), Theme view (grouped by cluster), Page view (grouped by product page, parsed from your component paths). Same specs, three angles.
The spec leaves Circuit as code.
This is the handoff — the spec lands in the tool you build with. Claude Code, Cursor and GitHub, connected over MCP, so the spec arrives where the work happens.
Circuit runs an MCP server, so Claude Code and Cursor pull your specs, priorities and feedback live. The agent reads the current spec, not a copy you pasted an hour ago.
circuit.priorities, circuit.spec, circuit.ask and circuit.act. The agent fetches the ranked list, pulls a full spec, asks questions of your feedback, and acts — all without leaving the terminal.
Turn a spec into a GitHub issue, with the customer context attached. Circuit checks for duplicates first, so you open the existing issue instead of a second one.
The customer who asked is the first to know.
When a spec ships, Circuit notifies the customers whose feedback fed it — with the line they sent and what changed. Closing the loop is the default, not the afterthought.
Mark a spec shipped and Circuit finds every customer whose feedback informed it. They hear from you before they have to ask.
The notification shows the exact feedback they sent, alongside what you built. The customer sees they were heard, specifically.
Circuit drafts the message in your brand voice and prepares the recipient list. You approve the send — sensitive accounts and half-addressed concerns stay under your control.
Shipping isn’t the end. It’s what Circuit learns from.
When a ticket closes, Circuit asks one question — did this resolve what the customers asked for? The answer updates the priority and feeds the memory layer, so the next brief in the same area starts with what you learned in this one. The loop closes, and the graph gets sharper.
Learn more about the Circuit Delivery suite.
One build-ready spec from the feedback behind a priority, cited line by line.
Sequenced by impact, not by date — hand any card to Cursor or Claude Code.
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.
Asked and answered.
Where does the spec come from?
Q1From the customer signal behind a priority. Circuit clusters the feedback, then drafts a structured spec with five sections — what to build, why it matters, customer voice, files to touch, done when. You edit a draft instead of writing one.
What’s the difference between a brief, a spec and a build?
Q2They’re the same artifact. The database calls it a build. The product UI calls it a spec. We say “brief” when we mean the early draft. One row, one document, one citation chain — opened from anywhere.
How does the roadmap decide what’s next?
Q3One button scores every spec by impact and recommends a bucket — Backlog, Later or Next. You can override any card; Circuit remembers what it suggested so you can always reset.
What is the spec map?
Q4A view of every spec your codebase has ever produced, organised by folder, theme or product page — with a blast-radius label on each spec (contained, moderate or cross-cutting), so you can see what’s safe to ship at a glance.
How does it work with Cursor and Claude Code?
Q5Connect over MCP and the coding agent pulls your specs, priorities and feedback live — no stale copy-paste. Or copy any spec as a prompt and paste it straight in.
What does codebase-aware mean?
Q6When you connect your repository, Circuit reads nine signals from it — file structures, conventions, related issues, tests, recent merges and more — and weaves them into the spec, so it fits your codebase instead of describing an ideal one.
Does Share Back send emails automatically?
Q7It drafts them and prepares the list. You review and approve the send. Loop-closure is the default behaviour, but the judgment of whether a specific message is right stays with you.
Delivery is available on all plans.
See pricing →