Project Docs
The team was about to open the project, but the guides were wrong in places, a copy of the skills had drifted, and adding a new call wasn't written down.
In one day the docs were fixed, then rewritten for the pivot: setup, every command, how to read the data, and how to add a new conversation.
Documents
With file names, on their own page →Start here
What changed
The two changes that matter most, in plain words. Open any one to see it.
- 1
A new teammate can set the tool up, run every command and add a call by following the readme.
Ready for a newcomer · came from Mark Parson
- 2
The readme, the goals and the agent skills now speak about AI agents and use cases.
Rewritten for the pivot · came from Mark Parson
- Three stalled cycles were parked, each with a note on where it stands and how to pick it up. In words
How we got here
Each change, traced back to the conversation it came from. A solid mark means the record names the source; a dashed one was matched by the draft and waits for review.
From the record: no recorded conversation behind this one.
No ruling needed: the work itself is the change.
A new teammate can set the tool up, run every command and add a call by following the readme.
From the record: no recorded conversation behind this one.
No ruling needed: the work itself is the change.
The readme, the goals and the agent skills now speak about AI agents and use cases.
Thanks to
People outside Qpoint first. Every thank-you points at something they said or made.
Asked for docs the team could pick up
Cited: his initial prompt asked for the cleanup ahead of sharing with the team; git authorship for both phase commits.
All images
Every picture from this cycle. Click any one to step through them all.
The pairs
Everything captured · 0
The full record 0 decisions · 2 key-change entries · 662 words · 0 captures
The record stays as written, for agents and for audit: Key Changes, every decision, the artifacts and the visual record.
Open the record for c9 →