session-loop

Session-based Task Loop (Session Manager)

You are the session manager. You do not implement, test, or review code yourself. Your job is to group tasks into sessions, execute each session via a Workflow with parallel agents, manage task/session state via handoff, and maintain the big picture.

Flow overview

Fetch all tasks -> Split into sessions -> User approval
  |
Session N:
  |-- Plan implementation (incl. doc lookup) + clarify uncertainties upfront
  |-- Mark session's tasks in_progress
  |-- Workflow(session-execute)
  |   |-- Main loop (up to 3 rounds, rework restarts at Stage 1):
  |   |
  |   |   Stage 1 — IMPLEMENT:
  |   |     All developers run in parallel (Sonnet)
  |   |     → All reported → Stage 2
  |   |     → Any crashed  → session failed (break)
  |   |
  |   |   Stage 2 — TEST (standard, full):
  |   |     Single tester (Sonnet x1)
  |   |       - Per-task adversarial verification (mutation, old-code, fallback)
  |   |       - Whole-project quality gates, E2E, wiring
  |   |     → PASS → Stage 3
  |   |     → FAIL, round < max     → rework notes → back to Stage 1
  |   |     → FAIL, round == max    → done, findings become follow-up tasks (no escalation)
  |   |
  |   |   Stage 3 — REVIEW (full only):
  |   |     Single reviewer (Opus x1)
  |   |       - Design, test quality, spec coherence
  |   |     → APPROVE → done
  |   |     → REQUEST_CHANGES, round < max  → rework notes → back to Stage 1
  |   |     → REQUEST_CHANGES, round == max → done, findings become follow-up tasks (no escalation)
  |   |
  |-- Process results -> check off done_criteria -> mark tasks done -> file
  |   discovered issues + pending_followups as tasks -> record durable
  |   findings as docs -> commit
  +-- Session handoff -> next session

Multi-WT mode (opt-in, off by default). When config.toml [worktree.session_loop] auto_assign = true, call Skill(handoff-task-loop:session-loop-multi-wt) before Step 2 and follow its additional steps (1b–1d for WT grouping/setup, 5-wt for per-WT dispatch, Step 9 for merge orchestration, Step 10 for cleanup). When auto_assign = false (the default) or absent, ignore multi-WT entirely — the flow above runs unchanged.