TODO Execution Process
To close: Write the Outcome (skill, grammar, page registry, four runs) · Move to HISTORY.md
last activity Sep 25
Mark's page-by-page meeting notes became work by hand, and the hand-offs leaked: lost lines, misread fragments, and every helper briefed one by one.
A todos skill now reads the notes straight from Logseq and writes one plan per page. Its first run made 17 plans, all carried out that day, one page at a time.
Documents
With file names, on their own page →What changed
The three changes that matter most, in plain words. Open any one to see it.
- 1
Each page in Mark's notes becomes one plan that a fresh helper can carry out without being briefed again.
One plan per page · came from Mark Parson
- 2
The skill reads the notes straight from Mark's journal, so nothing is lost in copy and paste.
Notes read straight from Logseq · came from Mark Parson
- 3
Before each page, Mark reads a short summary and fixes his own shorthand; after it, he reviews what changed.
One page at a time, with a preview · came from Mark Parson
- When someone in a review says something worth keeping, it goes in a Voices list instead of disappearing. 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.
c94-D1 Build the skill first, then test it on the 2026-09-24 notes; those notes are not planned by hand. — Mark Parson
c94-D4 Plans are numbered in the order pages appear in the notes, with a separate run order for dependencies. — Mark Parson
Each page in Mark's notes becomes one plan that a fresh helper can carry out without being briefed again.
From the record: no recorded conversation behind this one.
c94-D2 No copied notes file: the skill reads the block straight from the journal and quotes it word for word in the run's README. — Mark Parson
The skill reads the notes straight from Mark's journal, so nothing is lost in copy and paste.
From the record: no recorded conversation behind this one.
c94-D5 Plans run one page at a time, with a preview before each and a review after. — Mark Parson
Before each page, Mark reads a short summary and fixes his own shorthand; after it, he reviews what changed.
Thanks to
People outside Qpoint first. Every thank-you points at something they said or made.
His spend question showed voices had nowhere to go
In the 2026-09-24 review notes, his line asking whether his finance team could predict the month's spend was the example the process review used for remarks that got lost. Runs now route such lines to a Voices list.
Turned his own note-taking into a routine
Asked for the process, named the skill, ruled that notes are read straight from the journal, and corrected each plan's shorthand at its preview.
All images
Every picture from this cycle. Click any one to step through them all.
The pairs
Everything captured · 0
The full record 8 decisions · 4 key-change entries · 1,032 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 c94 →