# Build day

One focused day a week to move projects forward, because weekday evenings rarely happen. This is the routine I run.

## During the week: capture, don't decide

- Whenever something comes up (a bug, an idea, something to test), record a quick voice note or jot it down in one running list.
- Don't sort it. Don't start it. Just catch it.

This week's list:

-
-
-

## Build day morning: turn the list into briefs

- [ ] Paste the week's list into an AI chat and ask it to turn each item into a separate task brief (the format in `03-task-brief.md`).
- [ ] Read each brief. Cut anything vague, and split anything big.
- [ ] Put them in order. Anything touching the same files goes one after another.

```
Here's my list of things to do on my project this week:

[PASTE LIST]

Turn each one into a separate task brief with: a one-sentence task,
what exists and which files it probably touches, numbered requirements,
what not to change, and how I'll check it's done. Flag anything that's
too vague to brief, or too big for one task.
```

## Build day middle: hand off and let it run

- [ ] Give the agent the briefs, one at a time or as a batch with a commit after each.
- [ ] Approve plans, answer questions, and step away while it works.

## Build day afternoon: the audit

The part people skip, and the part that matters.

- [ ] Go through `05-review-checklist.md` for every task.
- [ ] Anything not right becomes a new, sharper brief.
- [ ] Push, and check the preview links.
- [ ] Merge what's ready.

## End of the day

What shipped:

What's carried to next week:

One line for the memory file: