Nightly Build System

How It Works

1. Build Queue (memory/build-queue.md)

Tasks accumulate throughout the day from:

• Your Obsidian todos tagged #agent
• Heartbeat-detected opportunities
• Manual additions ("add X to the build queue")

2. Nightly Build (Cron: 23:00)

At 23:00, a Sonnet-powered session:

1. Reads the build queue
2. Picks the highest-priority task
3. Spawns a Builder sub-agent with the task
4. Builder implements the feature/fix
5. Spawns a Reviewer sub-agent to check quality
6. If not approved → back to Builder with feedback
7. Max 3 iterations → commit or park with notes
8. Reports results to your channel

3. Morning Report

You wake up to:

• What was built
• What was committed
• What got parked (and why)
• Updated build queue

Build Queue Format

## Pending Tasks
- [ ] [P1] Add error handling to webhook processor
- [ ] [P2] Create dashboard component for health data
- [ ] [P3] Refactor calendar integration tests

## In Progress
- 🔨 Add pagination to search results (started 23:02)

## Completed
- ✅ Fix cron delivery routing (2026-02-14, 3 iterations)

Why This Matters

Your agent has downtime every night. This turns dead hours into productive build cycles. The Builder-Reviewer pattern catches bugs before you see the code.

Includes

• SKILL.md with complete build loop logic
• build-queue.md template
• Cron job config (23:00 nightly)
• Sub-agent spawn configurations
• Quality gate definitions