three-shifts

Files (4)

• PLANNER.md
• SKILL.md
• config.md · references/
• cycle-executor-v2.md · references/

SKILL.md (first lines)

# Three Shifts v3 — Daily Standup Engine

**Architecture:** Plan 3x daily → deliver for approval → execute in main session.

**Why v3:** V2 had a 15-minute autonomous cycle executor that never worked — state machine deadlocked for 19 days, burning ~27M tokens on no-ops. V3 removes it entirely. Plans are generated by cron, execution happens through normal conversation when the user approves.

---

## How It Works

1. **Planner cron fires** (6 AM, 2 PM, 10 PM) — reads context, generates a prioritized task list
2. **User reviews** — approves, modifies, or skips
3. **Agent executes** in main session — when the user says "go" or gives specific instructions
4. **Daily memory** captures what was done — next planner reads it for continuity

No file-based state machine. No autonomous executor. The main session IS the executor.

---

## File Structure

```
shifts/
├── tasks.md        # Current shift plan (generated by planner)
├── context.md      # Stack, constraints, known pitfalls
└── state.json      # Shift metadata (which shift, approval status)
```

### tasks.md

Generated by the planner each shift. This is a task list, not a state machine.

```markdown
# Morning Shift — 2026-03-13
Approved by: user | Approved at: 6:15 AM CST

## P1 (Must do)
1. Fix bootstrap key server (keys.everclaw.xyz returning 404)
2. Test installer on fresh Linux environment

## P2 (Should do)
3. Update MEMORY.md with yesterday's work
4. Review open PRs across EverClaw repos

## P3 (Could do)
5. Memory file maintenance (archive >7 day old dailies)

## Blocked/Waiting
- XMTP agent-to-agent — blocked on BASE_WALLET_PRIVATE_KEY
```

### state.json

Minimal metadata for the planner to read between shifts:

```json
{
  "shift": "morning",
  "date": "2026-03-13",
  "status": "approved",
  "approvedAt": "2026-03-13T06:15:00-05:00",
  "approvedBy": "user"
}
```

Status values: `planned` | `approved` | `skipped`

### context.md

Living document of constraints and lessons. Updated by the agent when something new is learned.

---

## Shifts

| Shift | Cron | Window | Character |
|-------|------|--------|-----------|
| Morning ☀️ | 6:00 AM | 6 AM – 2 PM | Comms, decisions, urgent items |
| Afternoon 🌤️ | 2:00 PM | 2 PM – 10 PM | Deep work, building, coding |
| Night 🌙 | 10:00 PM | 10 PM – 6 AM | Research, maintenance, cleanup |

All times in user's local timezone.

---

## Planning Phase

**Model:** `venice/kimi-k2-5` (cost-efficient, good at structured plans)

See `PLANNER.md` for the full planner instructions.

### What the planner reads:
- `shifts/tasks.md` — previous shift's plan (check for incomplete items)
- `shifts/context.md` — rules, constraints, pitfalls
- `shifts/state.json` — previous shift metadata
- `memory/daily/YYYY-MM-DD.md` — recent activity
- `MEMORY.md` — active projects (⚡ Active Context section)

### Plan format:

```
☀️/🌤️/🌙 [SHIFT] SHIFT PLAN
Date: [DATE] | Window: [START]–[END] CST

P1 (Must do):
1. [Task] — [Est. time] — [Why now]

P2 (Should do):
3. [Task] — [Est. time]

P3 (Could do):
5. [Task] — [Est. time]

Blocked/Waiting:
- [Item] — [Blocker]

Reply: "Approve" / "Skip" / "Add: [task]"
```

From EverClaw/buddybots.org, MIT.

More from EverClaw/buddybots.org