Direct your agents
Your agent knows what to build before it starts.
Each job gets one spec: what customers asked for, the files to change and how you'll know it's done.
Without it
The agent builds what it guessed you meant.
Nobody remembers which customer asked for it.
Done means whatever the agent says it means.
The spec
Five sections, one page every agent reads.
Problem · Evidence and direction · What to build · Files to touch · Done When
What your agent does with the spec.
The customers' words stay on the spec, so the next agent, in any tool, starts from the same page.
- Writes it from the evidence on the priority.
- Names the real files it will change.
- Writes Done When lines it can check.
You, your agent or Ask writes it.
Annsa keeps the evidence. It never writes a spec on its own.
You
Write it yourself, or change any section your agent wrote.
Your agent
Claude Code, Cursor, Codex and Grok write it over MCP, reading your repo themselves.
You stay in control
Your words stay yours.
What you write is never overwritten by Annsa or an agent. When a call is yours, the agent asks, with the options and its pick.
What's inside
- Sections
- Problem, Evidence and direction, What to build, Files to touch and Done When
- Written by
- You, your agent over MCP, or Ask. Annsa never writes a spec on its own.
- Codebase-aware
- When you ask for one, Ask writes it from your connected repo.
- Done When
- The agent records a receipt for each line it checked and says which ones it couldn't.
- Agents read it with
- annsa.spec, over remote MCP at app.annsa.ai/mcp
Questions people ask.
Q1
How does my agent read the spec?
Over remote MCP at app.annsa.ai/mcp, with annsa.spec. The first run opens a browser sign-in, and there's nothing to install.
Q2
How do I know the work matches the spec?
Before shipping, the agent records a receipt for each Done When line it checked and says which ones it couldn't. Receipts don't block a ship.
Q3
What does connecting GitHub add?
Annsa reads 16 signals from your repo, like the README, the directory structure and recent commits. You can also ask Annsa for a codebase-aware spec, and Ask writes it from your repo.
Q4
Does a merged PR mean it is live?
No. Annsa never deploys. A merged pull request that names the priority marks it shipped; deploying stays yours.