Course contents
Capstone: Your Weekly Report System
Build a complete standing system end-to-end: brief, skill, schedule, and two weeks of reviewed runs.
The capstone assembles the whole course into one working system you'll actually keep: a weekly report that researches, compiles, formats, and delivers itself — with you as editor-in-chief. Pick a report someone (possibly you) genuinely needs every week: team update, client digest, market summary, content plan.
Stage the workspace
Create a project folder with a brief.md: who the report is for, the sections in order, tone, where each input lives (files, inbox, sites to check), and a "what matters most" summary at the end.
Verifybrief.md answers: audience, sections, sources, tone, definition of done.Produce issue #1 interactively
Run the report with Claude while you watch, correcting as you go — section order, depth, which numbers matter. Iterate until you'd genuinely send it.
promptRead brief.md, then produce this week's report as report-[date].md. Ask me anything ambiguous rather than guessing.VerifyYou would send this issue to its real audience without edits.Capture the recipe as a skill
Freeze the working session into a reusable SOP.
promptTurn what we just did into a skill called weekly-report: inputs, section order, formatting, tone, and the checks you ran before finishing.VerifyThe skill exists; a fresh session with just "do the weekly report" reproduces the format correctly.Schedule it and review two cycles
Schedule the report for your real deadline (Friday 7am beats Monday panic). Review the next two automated issues line-by-line before relaxing into spot-checks. Refine the skill with anything you correct twice.
promptEvery Friday at 7:00 AM, run the weekly-report skill and notify me when the draft is ready for review.VerifyTwo consecutive scheduled issues arrived correct. You now run a standing system — congratulations, that's the whole loop.