Daily Driver
Routines, artifacts, and work that runs on a schedule
Session two turns last session's skills into a week that runs on rails. We build a four-week content calendar as a live artifact, put a weekly report on an actual schedule and wait for the first one to land on screen, then draft an outbound sequence to the ICP you already wrote. Every routine leaves with one line: what it produces, when, and who checks it before anything reaches a customer.
Session one is Tuesday Aug 25 at Workuity Biltmore and Wednesday Aug 26 at Workuity Chandler, evenings at 6:00 PM. Same session — pick the room that works. Nights two through four announced soon; watch Discord and the Meetup calendar.
Venue sponsor: Workuity. Format: the host builds live on screen. Bring a laptop and work along, or just watch — nobody is put on the spot.
Why this session
The gap between people who get value out of these tools and people who don't isn't prompting skill. It's whether anything happens when they aren't typing. A routine is three parts — a skill, a trigger, and a checkpoint — and most people build the first, skip the second, and are vague about the third.
What we cover
- 01
What a routine actually is
A skill, a trigger, and a checkpoint. Drop any one of the three and you're left with either a chat log or an unsupervised robot with your name on it.
- 02
Artifacts vs live artifacts
A dead artifact is generated once and rots. A live one gets edited, appended to and read back next week. The difference is a habit, not a file format — and regenerating throws away everything you learned since.
- 03
The content calendar, built live
Four weeks, worked backwards from questions your ICP actually asks. Then we add one entry by hand in the room, because that's the move that keeps it alive.
- 04
Scheduled tasks, on screen
The scheduler in ChatGPT and the one in Claude, both demoed for real. Same pattern, different buttons — plus the cron version for anyone who'd rather own it outright.
- 05
The weekly report
Three to five numbers you can genuinely obtain, under 200 words, in plain English. Scheduled during the session, and we wait for the first run to arrive rather than assuming it did.
- 06
Outbound, drafted
Your ICP into twenty named accounts with a reason each, then a sequence written to a folder. You send every one of them by hand. Nothing sends itself, tonight or later.
- 07
The checkpoint rule
One written line per routine naming who reviews what. A checkpoint you never actually read isn't a checkpoint, and unread automation is how a wrong number ends up in front of a customer.
You leave with
Three routines running on your own business, each with a written checkpoint line naming the human who reads it.
To follow along
A laptop, your files from session one, and whatever numbers you can already see — signups, orders, visits, replies. Free accounts cover most of the evening; scheduled tasks sit behind a paid plan on both ChatGPT and Claude today, so we demo them on screen and show the cron path for anyone not paying. Missed session one? Come anyway — we'll point you at the two skills to run first.
Afterward
Nothing is required. It compounds if you run the same work on your own product. The suggested output:
02-routines/ — if you want somewhere to put it: your four-week calendar, the weekly report format and its first real run, the outbound drafts, and a checkpoint line for each of the three.
Everything is open source. Missed the session? It's archived in Discord.
The session kit
Slides, a follow-along guide and skill files. Free to download, room or no room.
.claude/skills/.Download (5) ↓Install this session's skills
curl -fsSLO https://www.shipai.club/skills/day-zero-02-coworking-with-ai.zip
unzip -o day-zero-02-coworking-with-ai.zip -d .What's in the bundle
/content-calendarSKILL.mdBuild a four-week calendar from what the ICP actually asks, kept as a live artifact you update rather than regenerate. Use once voice and ICP exist.
/weekly-reportSKILL.mdPut a short weekly numbers report on a schedule so it arrives without being asked. Use once there are numbers you can actually obtain.
/icp-builderSKILL.mdDefine a B2B ICP tight enough to write one email to, and build the named account list. Use before any outbound.
/outbound-sequenceSKILL.mdWrite cold outbound email that gets replies, plus the follow-up cadence and the graceful no. Use once the account list exists.
/social-postSKILL.mdTurn one thing you actually shipped into platform-native post drafts for X and LinkedIn, in your own voice. Use when there's a real artifact and no post yet.
Every program skill is on the skills page.
The community online
Recaps, archive links, questions between sessions, everyone else's work in progress.