1. What to Build — a clear, actionable task statement. One sentence describing exactly what to implement.
2. Why It Matters — business context: who's affected, revenue impact, urgency.
3. Customer Voice — a key verbatim quote (5–20 words) plus 3 supporting quotes with user type and emotion.
4. Files to Touch — suggested locations with (new) or (modify) labels, from your connected repository.
5. Done When — clear exit criteria.
| Status | Meaning | Next action |
|---|---|---|
| Ready | Waiting for action | Start building |
| Building | In progress | Complete and ship |
| Shipped | Feature deployed | Share back with customers |
| Shared | Complete, customers notified | Monitor feedback for V2 |
Click any priority to see the spec inline. The edit icon opens it in an editor — make changes, then Save. Every save becomes a new version.
The refresh icon regenerates against the latest feedback, and a Refresh badge appears automatically when new feedback has moved the scope. Refresh is section-aware: anything you edited by hand is preserved and only untouched sections regenerate.
Click V1, V2 and so on to compare. Two things create a version — new feedback arriving on a shipped spec (automatic), or you editing or refreshing (manual). All versions are kept indefinitely.
Copy takes the title, metadata and every section for pasting into Cursor or Claude Code. Export downloads it as .md, and you can batch-export several from the priorities list. Arrow keys move between specs; Enter expands a priority.
The feedback accordion lists every item that fed the priority. Remove one that was miscategorised and it isn't deleted — it returns to the pool and gets re-categorised on the next sweep, possibly into a different priority.
Mark as Shipped opens Share Back.
| Channel | What happens |
|---|---|
| Branded notification to eligible customers | |
| Survey banner | Banner shown to returning visitors |
| Both | Email plus banner (default) |
Review the recipients — anyone whose email is on file — and uncheck to skip, or Skip entirely to keep the spec at Shipped without notifying. Emails use your workspace branding from Settings → Integrations → Survey → Notification branding.
After sending, the spec moves to Shared — the final stage. A ship memory is recorded at this point: theme, volume and customer segment at time of ship. That's what Annsa learns from. New feedback on the same theme afterwards feeds a V2. Annsa also asks for a thumbs up or down on spec quality, which takes one click and improves future specs.
Solo-founded in Sydney in 2025. Launched February 2026.