Agentic Workflows
A look at how we use AI helpers across all our projects found the daily work strong but the shared plumbing weak: copied files, no automation.
Nothing was built here. The cleanup half was done by c69; the rest, like shared plugins and automatic checks, waits as notes for a future cycle.
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
The helpers themselves were well built; sharing them between projects, and checking them, was not.
An audit of how we work with AI helpers · came from Mark Parson
- 2
c69 did the tidying half: one skill format, a sweep of stale cycles, and written conventions.
The cleanup happened in c69
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.
The helpers themselves were well built; sharing them between projects, and checking them, was not.
From the record: no recorded conversation behind this one.
No ruling needed: the work itself is the change.
c69 did the tidying half: one skill format, a sweep of stale cycles, and written conventions.
Thanks to
People outside Qpoint first. Every thank-you points at something they said or made.
Held it for full attention
Asked for a walkthrough-style cycle he would drive step by step to understand each mechanism, rather than a batch migration, and parked it until he could.
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 · 1 key-change entries · 190 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 c53 →