If every new campaign starts with explaining the same process again, the missing asset is a playbook. We’ll use Claude Code to apply stable rules to changing people, dates and approved material, then hand the plan to another producer.
Kabo, an AI agent for creator research, helps with unresolved reference questions. Claude Code uses a small project playbook to produce consistent handoffs across campaigns.
Build the playbook we can use for the next campaign
Our arts nonprofit runs another workshop every month. The people change, but the same questions come back: is the venue information approved, can we use the photos, and who reviews the final post?
We’ll put those repeatable checks in a short project playbook. Claude Code can then prepare a campaign packet from changing facts, rather than making the next volunteer reconstruct our process from a calendar.
Prepare the materials for this Claude Code task
Keep recurring rules separate from this workshop’s facts. A reviewer’s availability next Monday belongs in the campaign files, not in a permanent instruction.
[ ] CLAUDE.md — Stable output and review conventions. [ ] planning-rules.md — What every publishable row needs and how to mark blockers. [ ] campaign.md — Current workshop dates, approved venue details and audience. [ ] assets.csv — Asset owner, approval status and alternative material. [ ] availability.md — This campaign’s writers, volunteers and reviewers. [ ] handoff/ — Calendar proposal, blockers and a short note for the next producer.
Write rules that can be checked
“Make the calendar realistic” is hard to inspect. A rule such as “every release row needs an asset, an owner and an earlier review task” gives us a concrete check. Keep the playbook small enough that a volunteer can understand it too.
Save these checks as planning-rules.md. In CLAUDE.md, note that calendar tasks should read that file; keep this campaign’s people and dates in its separate notes.
For each proposed release, name the owner, approved source asset and review task. Mark a row BLOCKED if a required asset, fact or approval is missing. Never replace missing venue or accessibility facts with a guess. Put capture, writing and review before the proposed release. Keep campaign-specific people and dates in campaign.md or availability.md. Return the calendar plus blockers.md; do not publish externally.
Connect Kabo
Open the content project, install Kabo for Claude Code and complete sign-in. For a direct server connection, follow the setup guide.
Try the rules on one incomplete row
Before generating the calendar, give Claude Code a deliberately unfinished brief. Suppose a venue walkthrough has an owner and filming date but no asset approval. A useful result is BLOCKED: confirm permission before using the footage, not a polished release slot.
This small dry run tells us whether the rules are doing any work. If everything comes back “ready,” ask which evidence cleared each required field.
Read planning-rules.md, campaign.md, assets.csv and availability.md. Test one proposed venue-walkthrough post against the rules. For each required field, cite the file value that satisfies it or mark a blocker. Do not fill missing facts. Show the test result before creating the full calendar.
Generate a packet a volunteer can pick up
Once the test makes sense, ask for three deliverables: the proposed calendar, a blocker list and a short handoff. The handoff explains the next action for each person; it should not be a second copy of the schedule.
Use Kabo only for a specific explanation question, such as how comparable public workshop videos introduce an unfamiliar activity. Put that research in the relevant brief, while the organizer supplies the event facts.
Apply planning-rules.md to the current campaign and assets. Write handoff/calendar.csv with task IDs, owners, assets, dependencies, review dates and proposed releases in Europe/London time. Write blockers.md with the person who can resolve each gap. Write a short handoff note for the next volunteer. Include an approved fallback asset only where one is listed; do not invent replacement filming.
Update facts without turning every problem into a permanent rule
If Saturday filming is cancelled, change the campaign’s availability and available assets. Claude Code should rerun the relevant checks and identify affected tasks. That cancellation is not a new global rule saying “never film on Saturdays.”
If the same review failure keeps happening across campaigns, then discuss a lasting rule change. For example, requiring an asset approval reference is reusable; naming this month’s reviewer in CLAUDE.md is not.
Saturday filming is cancelled. Recheck only the tasks that rely on it using the approved assets already listed. Update the campaign packet, list the blocked tasks and give the next volunteer one clear action per owner. Explain whether this event requires a campaign fact update or a change to planning-rules.md; don’t change stable rules automatically.
Reuse the process, refresh the inputs
At the next workshop, replace campaign.md, the asset inventory and availability. Keep the agreed rules and rerun the one-row readiness test before generating another packet. Review assignments in Google Sheets.
Need a new teaching topic first? Use the Claude Code ideas workflow. For a one-off date change in an existing plan, the Codex calendar example shows a focused patch instead.
Worked examples are illustrative. Product screenshots show existing Kabo web results, not a run of the example in this guide. Use your own materials and the evidence returned in your task.