Log the Practice Session
Close out today's practice properly: log what was actually worked with honest minutes and tempo marks, and set up tomorrow's session so the next sit-down starts with intent instead of noodling. Locks the honest picture of the session FIRST, then logs it into the practice record, then writes tomorrow's targeted plan. Use for logging a practice session, ending today's practice, planning tomorrow's practice, and 'log my practice'.
Steps
Entry step: scope. Each step names the specialist role it wants; the full working prompt is expandable.
- Scope the sessioncoachentry
honest picture of today: pieces, minutes, tempos, trouble spots
Show working prompt
Get the honest picture of today's session before logging a minute of it. Step 1: read practice.json and repertoire.json from the workspace — the streak, the pieces in rotation, and where each one stands. Step 2: confirm with the owner what actually happened today: which pieces, honest minutes (the ones at the instrument, not the ones planned), tempo marks reached, and the spots that fought back. Step 3: write an acceptance-criteria checklist ('today's session is logged with date, minutes, and piece', 'trouble spots recorded by bar or passage, not vibes', 'piece states in the repertoire updated where today changed them', 'tomorrow's plan targets the trouble spots with concrete tempo marks'). Call write_task_note with the minutes + pieces + checklist and write notes/scope.md. - Log the sessioncoach
today's entry into the practice record, piece states updated
Show working prompt
Log today exactly as it went. Step 1: record the session through the project's practice capabilities — date, minutes, piece(s), tempo marks, and what felt solid versus mushy, in the owner's own words. Step 2: update the piece states in the repertoire where today moved them — forward or backward; honest beats flattering. Step 3: confirm the log landed by reading practice.json back — today's entry must be there with its date, minutes, and piece. Call write_task_note with the entry as logged.
- Write the close-outcoach
today in two lines, streak state, tomorrow's targeted plan
Show working prompt
Close the day and open tomorrow. Step 1: write today in two honest lines — what got the minutes and how it went. Step 2: state the streak — how many days running, and what today did to it. Step 3: write tomorrow's plan: the specific passages to hit (by bar number), the metronome mark to start at and the mark to reach for, and one thing to leave alone because it is already working. Step 4: keep it encouraging and true — a coach's note, not a report card. Write report.md and call write_task_note with tomorrow's top target.
- Evaluatereviewer
Grade the deliverable against every acceptance criterion. All pass → finish; any fail → loop back and fix the gap.
Show working prompt
Open report.md and practice.json and verify every criterion from notes/scope.md: today's entry is in the log with date, minutes, and piece matching what the owner reported; trouble spots are recorded by bar or passage; repertoire states moved where today moved them; and tomorrow's plan names specific passages with metronome marks. Write PASS/FAIL per criterion; on any failure, name the gap and loop back to report. Then route — this is the whole point of the loop: - **Every criterion PASSES →** call `advance_task_step({ ref, stepId: "evaluate", next: "finish" })`. - **Any criterion FAILS →** write the specific gaps to notes, then call `advance_task_step({ ref, stepId: "evaluate", next: "report" })` to loop back. The builder fixes exactly those gaps. Never route to `finish` while any criterion is unmet. The build phase's completion gate already blocked a grossly-incomplete deliverable; your job is the judgment an automated check cannot make (does it actually work, read well, look right). After ~3 unproductive loops, stop and report DONE_WITH_CONCERNS so the user can step in. - Finishdeveloper
All acceptance criteria met. Stamp a short summary and report DONE.
Show working prompt
Every acceptance criterion passed. Write a one-paragraph DONE summary to task notes via `write_task_note`: what was built, the deliverable path(s), and a one-line confirmation that each criterion is met. Then report DONE.
Triggers
Phrases that suggest this craftbook to a crew.
- log my practice
- log today's session
- just finished practicing
- set up tomorrow's practice
- close out the practice session
Source
View this craftbook on GitHub · MIT license