The document
The view opens on the two sections described in PRD structure, Features and API Access & Rules, with a header that rolls every entry into four counts: current, needs re-recording, failing, and need attention. A table of contents lists every section and entry with its status, so the state of the whole app is readable at a glance. Clicking an entry opens its drawer with the full evidence for that requirement:- the recording with its synced step timeline, a light/dark theme toggle, and playback speed control;
- Setup data and End state data, the database snapshots around the flow;
- Service calls (what the app sent), every captured payload;
- for access entries, the generated Who can do this / How access is verified text and the scenario transcripts.
Comments and collaboration
Review happens in place. Each item takes threaded comments from the gutter next to it, so feedback stays attached to the requirement it’s about: “this should say overdue, not late”, “confirmed: public read is intended here.” Threads resolve like any review conversation, and any thread can be sent to the appWriter agent with its full context. The agent receives the exact item and the conversation, makes the change (to the app, the PRD, or the tests, whichever is actually wrong), and reports back with a passing build and the evidence re-captured. Two drawer shortcuts skip the comment step when the ask is direct:- Ask Agent — on any item: opens the appWriter chat pre-filled with a pointer to this exact item, ending with an open line for what you want done. Pre-filled, not sent; you finish the sentence.
- Fix it — replaces Ask Agent on a failing item: the pre-filled message asks the agent to diagnose whether the app regressed or the test is out of date, fix the right side, and finish with a passing build. Add context (“I think it broke when we added priorities”) before sending.