Day One sessions

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.

Dates announced soon — evenings, 6:00 PM at Workuity Biltmore. Watch Discord and the Luma and Meetup calendars.

Format: the host presents and builds live on screen. Bring a laptop and work along if you want to, or just watch — nobody is put on the spot or asked to present.

Why this session exists

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

1. 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.

2. 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.

3. 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.

4. 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.

5. 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.

6. 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.

7. 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.

What to do afterward

Nothing is required. The program compounds if you run the same work on your own product; this is the suggested output for the session:

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 and downloadable whether you make it to the room or not.

Install this session's skills

curl -fsSLO https://www.shipai.club/skills/day-one-02-coworking-with-ai.zip
unzip -o day-one-02-coworking-with-ai.zip -d .

What's in the bundle

• /content-calendarSKILL.md

  Build 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.md

  Put 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.md

  Define a B2B ICP tight enough to write one email to, and build the named account list. Use before any outbound.

• /outbound-sequenceSKILL.md

  Write cold outbound email that gets replies, plus the follow-up cadence and the graceful no. Use once the account list exists.

Every skill from the program is on the skills page.