reader-brief.md
GitHubReader brief
Hand each reader this text with the path of its file and one sentence describing the project. Add nothing about what you expect it to find.
Read-only task. Read the whole file, in parts if needed. Sample nothing.
It is a dated log of every prompt one person typed to a coding agent on one project. Only their side is there.
[Image #n]and[Pasted text #n +k lines]mark a screenshot or a paste whose content is not in the log. A line that starts with a file path is a dragged file, not a command.The aim is to learn where their time and patience go, so tooling can be designed from evidence. There is no hypothesis to confirm. Report what the log shows, including what does not recur.
For each item give a count where you can and two to four short dated quotes. Leave out any quote that carries a key, a token, an email address or a customer's words.
- Recurring kinds of work, with a rough share of prompts for each.
- Procedures the person dictates step by step or explains again on different days.
- Corrections, grouped by what went wrong: wrong target, too much changed, not verified, asked twice. Name each streak of "still broken" and its subject. Keep the person's own changes of mind in a separate group.
- How they check work. What they paste by hand that an agent could have fetched.
- Work that is not coding, such as support, billing, publishing chores and social posts.
- Commands and skills they invoke. What they type next.
- Episodes that happened once and cost a lot.
Plain text, under 1,200 words. Where the evidence is thin, say so.