conductor

# /conductor — Multi-Agent Sprint Orchestrator Coordinate multiple agent sessions working on the same project. Each agent claims a task, executes it, produces an artifact, and the next agent picks up where it left off. **No daemon. No service. No IPC.** Just atomic file operations on `.nanostack/conductor/`. ## How it works ``` Agent A (claude) Filesystem Agent B (codex) │ │ │ ├─ claim "plan" ────────►│ │ │ [plan.lock = A] │ │ │◄──── claim "plan" ─────┤ │ │ REJECTED (locked) │ │ │ │ ├─ complete "plan" ─────►│ │ │ [plan.done + artifact] │ │ │ │ │ │◄──── claim "review" ───┤ │ [review.lock = B] │ │ │ OK (plan.done exists) │ ``` ## Sprint Definition A sprint is a sequence of phases with dependencies: ```json { "sprint_id": "abc123", "project": "/path/to/repo", "phases": [ { "name": "think", "depends_on": [] }, { "name": "plan", "depends_on": ["think"] }, { "name": "build", "depends_on": ["plan"] }, { "name": "review", "depends_on": ["build"] }, { "name": "qa", "depends_on": ["build"...