# Daily Cadence — Captain's Template

> Drop this into `~/command/cadence/daily/template.md` in your Command Kit.
> The day below is roughly how Max runs MaxShip — adapt to your rhythm.

## ⚓ Morning scan (first 30 minutes)

Before you ship anything, you orient.

- [ ] `git pull` across every active repo (yours + clients')
- [ ] Quick database scan — any new messages, inquiries, orders?
- [ ] KPI gauge: today vs. yesterday vs. rolling 7-day average
- [ ] Set today's priorities in Linear and GitHub

The point isn't to absorb every detail. The point is to know the shape of the day before you start.

## 🛠️ Build block (after the scan)

Lock in. This is when the captain ships.

- [ ] At least 1–3 PRs (push small + often beats waiting for a big one)
- [ ] Look for code to **delete** as readily as code to add
- [ ] Improve a tool/pattern the team uses
- [ ] Add or upgrade an automated cadence somewhere (nightly research, weekly review, etc.)
- [ ] Check the daily/weekly loops are still running clean

## 🎯 What to ship next

Decide using a triangle:

1. **Bug reports / fires** — does anything need stopping today?
2. **Team priorities** — what's blocking Tati / Ellen / a client?
3. **Your priorities** — the directional bets only you can make

If two of three are quiet, focus on the third.

## 🌙 End-of-day ritual

The most important 15 minutes of the day.

- [ ] Triple-check Claude has logged everything on a Linear ticket — with rich detail, not just headlines
- [ ] Every meaningful action gets a ticket number → that's the course-of-record
- [ ] Read tomorrow's plan back. Edit it before bed, not after coffee
- [ ] Close laptop. Walk away.

## Why this matters

Linear becomes the **journal of the work done**. Months later, you can ask "when did we add that? why?" — and there's a ticket with the answer. The discipline at end-of-day is what makes the company memory possible at all.

---

Maintained at `/log/cadence/daily` on max-ship.com.