Your Monday Morning Plan With Claude Code
The whole course, compressed
Here's this course compressed into what actually happens Monday morning.
Monday morning, in three moves
A reconciliation, a contract folder, a recurring report: the same shape as the spreadsheet reconciliation in Lesson 07 or the contract-folder tracker in the same lesson. Start with sanitized or non-personal data first, so questions of data governance don't have to be answered before the first attempt. This is practice 02, right-sizing the task (Lesson 06): inputs in hand, output defined, verifiable today.
Plan Mode is the Shift+Tab toggle from Lesson 05: the agent reads the files and proposes what it intends to do before touching anything. Use the shape of the demo prompts from this course as templates. Correct the plan before approving it, then spot-check the citations once the work is done rather than taking "done" at face value. This is practice 01 (brief before you delegate) and practice 03 (demand evidence, not assurances) together.
CLAUDE.md is the plain-text rules file from Lesson 08: five lines like "fiscal year starts in April" is enough to start. Write it, save the workflow as a skill, and keep the human signature on everything that ships. This is practice 04 (durable instructions) and practice 05 (drafted, not sent). Then show one colleague what happened.
Illustrative, not a documented case: someone picks the folder of vendor contracts sitting untouched since last quarter, runs the renewals-tracker prompt from Lesson 07 in Plan Mode, corrects one line in the plan before approving it, spot-checks three of the resulting citations against the source PDFs, then saves a five-line CLAUDE.md so the date format and currency rules never have to be retyped. The whole loop, start to finish, is closer to an hour than a day. That's a plausible order of magnitude for a first attempt, not a measured benchmark from a real deployment.
Why the third move is the one that matters
That third move, not the first two, is what actually spreads the practice through an organization. A single successful run that stays undocumented and unshared doesn't compound. It's a nice afternoon that has to be reinvented from scratch the next time someone needs it. Writing it down and showing one other person is what turns a personal win into something the team actually has.
Don't bring a hypothetical. Bring the actual task sitting on the desk right now, the one that's been "not quite worth delegating" for months. That's the task this course was built to finally move.
Checking what actually spreads
The whole course, in two sentences
Delegate to the machine. Keep the signature. Everything in between those two sentences (the plan, the evidence, the handbook, the review) is the discipline this course set out to teach, and it's now a complete loop: brief it, bound it, check it, write it down, sign it.
That's all ten lessons. Revisit any of them, or go straight back to your own desk and run the first one for real.
Reply here and it goes straight to Rod. Same as replying to one of his emails.
