Daily Driver

Four routines that run whether or not you remember them: a live content calendar, a weekly report that has already landed once, outbound drafted into a folder, and a written checkpoint for each. Nothing here sends anything.

Five-minute setup

Do this before the session starts, or in the first ten minutes while the framing happens. Nothing here is required to attend.

1. Have an agent installed

   Claude Code, the Codex extension, or whatever you already run. Every skill file below is plain markdown with frontmatter — it works in anything that reads a skills directory.

2. Get the skills

   Download this session's bundle and unzip it at the root of your project. It writes into .claude/skills/ and nothing else.

   unzip -o day-zero-02-coworking-with-ai.zip -d .

3. Point it at a real product

   An idea in a notes app counts. The skills read your repo, your site and your README before asking you anything, so run them from inside the project rather than a blank folder.

4. Make somewhere to put the output

   The skills write markdown and don't care where it lands. One folder per session — 01-voice/ through 04-agents/ — at the root of your project. Make tonight's before you start rather than mid-run.

The steps

1. 01

   Build the four-week calendar

   /content-calendar

   It reads 01-voice/skills/icp-profile/SKILL.md and works from the questions your buyers actually ask — the ones they type into a search box and the ones they ask you on calls. Eight slots across four weeks, two left empty on purpose, six entries dated in one file.

   Done looks like: Every row traces back to a question a real person asked, not a topic that sounds like marketing.

2. 02

   Make it live before you close the tab

   Three edits, made by you, right now — add one entry, move one, delete one you'd never write. The skill hands you the file and stops there on purpose. That edit is what turns generated output into a file you own, and from here on it gets updated, never regenerated.

   Done looks like: The file has at least one line in it the model didn't write.

3. 03

   Draft this week's posts, not the whole month

   /social-post

   Take one row off the calendar — something you actually did this week — and let it write the X version and the LinkedIn version separately, in the voice skill from session 01. Same artifact, different lengths, different openings. If there's nothing real to point at yet, skip the row rather than invent one.

   Done looks like: Two drafts in 02-routines/social/, each pointing at a link or a number, every claim in them marked verified or unverified, and nothing posted.

4. 04

   Schedule the weekly report and watch one land

   /weekly-report

   Three to five numbers you can genuinely obtain, in a report under two hundred words, in plain English. Pick your mechanism — both product schedulers sit behind a paid plan today, so cron is the free path if you're not paying — then run it once by hand.

   Done looks like: One report has actually arrived and you read it. Counts, not percentages, on anything small — fourteen customers can't carry a percentage. If it hasn't run once, it isn't set up.

5. 05

   Turn the ICP into twenty named accounts

   /icp-builder

   The profile from session 01 becomes a list of real companies and real people. The skill drafts it; you read every row. A list you haven't read is a list you won't send to.

   Done looks like: Twenty rows, each with a one-line reason that account is on the list. You cut at least a few.

6. 06

   Draft the sequence into a folder

   /outbound-sequence

   First touch, two follow-ups, and a break-up that doesn't grovel — short enough to read on a phone. It writes to 02-routines/outbound/ and stops there. Nothing in this program has your outbox.

   Done looks like: You'd reply to it if it landed in your inbox cold, and the send count is still zero.

7. 07

   Write a checkpoint line for every routine

   One sentence each: who reads the output, when, and what they do about it. If the honest answer is "nobody, ever", either delete the checkpoint or delete the routine — a rubber stamp is worse than no review, because it looks like one.

   Done looks like: Every routine in the folder has a named checkpoint you'd actually honour on a busy week.

What you leave with

02-routines/ — calendar.md with a hand-added entry, social/ with two drafts nobody has posted, weekly-report.md with its first real run beside it, accounts.md with twenty named accounts, outbound/ with drafts and nothing sent, and a checkpoint line per routine.

If you get stuck

Schedule not firing, or the product you use doesn't have one? Run it manually once and move on. The schedule is the wrapper; the skill is the value, and you can bolt a clock to it any evening this week.

Or ask in Discord — mentors and everyone else's work in progress are there between sessions.