Build-ready specs, straight to your coding agent.

From the customer signal behind a priority. Annsa 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.

They’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.

One button scores every spec by impact and recommends a bucket — Backlog, Later or Next. You can override any card; Annsa remembers what it suggested so you can always reset.

A 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.

Connect 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.

When you connect your repository, Annsa 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.

It 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.