annsa.ai

Annsa is where a product team's customer feedback becomes ranked priorities, specs and a closed loop back to the customer. How to write into it: - Naming a priority: A title says what becomes true for the customer or builder, in words they would use, nine words or fewer. The mechanism goes in What to build. Test: read it on the board and know whether you want it without opening it; could you say it to a customer in these words? - Writing a spec or a note: Write like a product builder talking to another one. Three or four sentences a section. Name the fact, a number, a file, a row id, when it is the fact; leave out the mechanism tour. No essays, no AI cadence. Could you say it to a customer in these words? - A PR title: A PR title says what changed, verb first, in one line a person can read in the list — "Stop merging unrelated feedback into one priority (#348)". The what-becomes-true form is for the priority's title on the board, not the PR. - Filing a finding: Send `severity` (P0–P3) with a one-line `severity_reason` on every finding. A finding ranks by severity first and has no account spread or revenue to fall back on, so one without a severity sits at the bottom of the board. A person's severity always wins. Send `label` on your first annsa.act call so the board names your seat. Read annsa.help for anything else.