Every requirement quotes its source
Every requirement quotes its source.
Drop in the contract, the customer’s emails, the kick-off deck and the spreadsheet. AI writes the spec from them, every requirement cites where it comes from, and the server checks each quote word for word before you see it.
Overtime export for payroll
In reviewRequirements
1.One row per person and day, with project and ticket.S2
2.Exports close on the 3rd working day of the month.S1 · p. 4
3.Columns in the order payroll imports them.S4 · Columns
Where the sources disagree
“Separator: comma.”S3 · slide 7 “Please use semicolons, our Excel is German.”S2
The spec follows S2, the newer source.
6 quotes checked word for word · 1 left out: not found in S3
- S1Framework agreement v3.pdfPDF · 14 pages · 2 Sep
- S2Anna Berg: Re: export for payrollEmail · 2 attachments · 9 Oct
- S3Kick-off.pptx12 slides, 1 hidden · speaker notes
- S4Payroll columns.xlsx2 sheets
- S5Whiteboard.jpgRead by AI
§ 6.2 Reporting. The contractor provides the monthly time report as a machine-readable file. Exports close on the 3rd working day of the month, after which corrections need written approval.
Theme · 14 customers · €182k a year
“We retype overtime into payroll every month.”
Most likely answered by ET-11 · Link all
| Ticket | Asked | Worth | RICE |
|---|---|---|---|
| ET-11 Overtime export for payroll | 14 | €182k | 336 |
| ET-19 Approve absences from Slack | 9 | €96k | 151 |
| ET-23 Bulk edit shifts | 6 | €41k | 64 |
Planned
Bulk edit shifts
38
Approve absences from Slack
27
In progress
Export for payroll
112
Shift swap requests
41
Shipped
Dark mode
64
Holiday calendar import
52
Voters hear when it starts and ships. No keys, no names.
The app’s own components, rendered with example data.
Sources the way they really arrive
PDFs, Word, PowerPoint, Excel, CSV, emails from Outlook or any mail program, screenshots and photos, up to 50 MB each. The server reads them and keeps where everything stands: pages, slides with their speaker notes and hidden slides, sheets, tracked changes and comments.
- Attachments of an email become sources of their own, one level down.
- Screenshots, whiteboard photos and scanned pages are read by AI, and marked so you can tell them from the file’s own words.
- Each source is dated by its own date, so the newer one usually wins.
Quotes the server checked
Every requirement quotes its source. Each quote is checked against the source text, ignoring line breaks and quote marks; what cannot be found is left out, and the result says so. A citation is a chip: click it and the source opens at its page, slide or sheet with the quote highlighted.
Where the sources disagree
When the deck says comma and the email says semicolon, the spec does not pick quietly. It gets a section that quotes both sides and says what it follows. Revisions keep the source numbers, and every change is a version you can restore.
From spec to tickets
Ticket keys in a spec become live chips with their status, and a tickets block becomes a table with how many are done. Create tickets breaks the spec down into briefs, and agents read the spec and its sources over MCP before they build.
Feedback tied to the tickets that answer it
One inbox for what customers ask for: by hand, from a call transcript, Intercom, Zendesk, email, Slack or the public roadmap. AI groups it into themes with how many customers and how much account value, and ranks the tickets by RICE.
A public roadmap customers vote on
Planned, In progress and Shipped columns follow their tickets. Visitors vote and send ideas with a confirmed email, and hear once when work starts and when it ships. They never see a ticket key, a title or anyone’s name.
Questions
What if AI invents a requirement?
It cannot slip through with a quote. Every quote is checked word for word against the source, and quotes that are not there are dropped before the spec reaches the editor, with a note that they were.
Which files can it read?
PDF, .docx, .pptx, .xlsx, .xls, CSV, .eml, Outlook .msg, PNG, JPEG, GIF, WebP, text, Markdown and HTML. Old .doc and .ppt, password-protected files, Pages, Keynote, Numbers and HEIC say why they could not be read.
Who sees the sources?
Everyone who sees the spec. The people who may write the spec add and remove sources; guests read the specs of the projects they work on.
Does it count as AI actions?
Writing a spec counts as one AI action. Reading pictures counts per batch of 6 pictures or 10 PDF pages; past the allowance, the source says its pictures were not read.
Give your next agent a brief.
Free for up to 10 people, with MCP for every agent. No credit card.