Skip to content

dispatch.md

Latest commit

 

History

History
132 lines (96 loc) · 3.18 KB

dispatch.md

File metadata and controls

132 lines (96 loc) · 3.18 KB
Raw

Sprint [XX] Dispatch — [Theme]

[One-line description of sprint goals] Created: YYYY-MM-DD

Sprint Goals

  1. Goal 1
  2. Goal 2
  3. Goal 3

Execution Traces

Chain 1: [Title] (P1)

[entry point] → [function] → [function] → [root cause]
Signal: [what's broken and observable evidence]

Chain 2: [Title] (P1)

[entry point] → [function] → [root cause]
Signal: [what's broken]

Chain 3: [Title] (P2)

[trace path]
Signal: [observable evidence]

Wave Assignments

Each agent's focus should reference the chain(s) above it is resolving.

Wave 0 — Planning (ORCHESTRATOR)

ORCHESTRATOR analyzes the codebase, writes execution traces, and generates this dispatch plan + all agent task docs.

Wave 1 — Foundation (no dependencies)

Agent Focus Est. Complexity
DATA [Data layer tasks] [1-10]
QA [Test/security tasks] [1-10]
INFRA [Infrastructure tasks] [1-10]
DESIGN [Design system/token/a11y tasks] [1-10]

Wave 2 — Backend (depends on Wave 1)

Agent Focus Est. Complexity
BACKEND [Handler/service tasks] [1-10]
SERVICES [Integration/service tasks] [1-10]

Wave 3 — Frontend (needs DESIGN specs + stable backend)

Agent Focus Est. Complexity
FRONTEND [Frontend tasks] [1-10]

Wave 4 — Review (needs finished code)

Agent Focus Est. Complexity
RED TEAM [Adversarial review of all branches] [1-10]

Wave 5 — Ship (depends on all)

Agent Focus Est. Complexity
LEAD [Merge + docs] [1-10]

Wave 6 — Assessment (ORCHESTRATOR)

ORCHESTRATOR grades each agent against the sprint mission, produces SPRINT-ASSESSMENT.md.

Merge Order

Run merge validation (build + test) after EVERY merge before proceeding. ORCHESTRATOR does not merge — it plans (Wave 0) and grades (Wave 6).

0. ORCHESTRATOR — plans sprint (Wave 0), grades agents (Wave 6) — no merge
1. DATA → main
2. DESIGN   → main
3. BACKEND   → main
4. SERVICES   → main
5. FRONTEND   → main
6. INFRA → main
7. QA    → main
8. RED TEAM — does not merge; produces findings report
9. LEAD    → main

Success Criteria

  • Criterion 1
  • Criterion 2
  • Criterion 3

Worktree Setup

SPRINT="sprint-XX"
PROJECT_DIR="$(pwd)"
PARENT_DIR="$(dirname $PROJECT_DIR)"
PROJECT_NAME="$(basename $PROJECT_DIR)"

for agent in backend frontend infra services qa data lead design; do
  git branch $SPRINT/$agent main 2>/dev/null || true
  git worktree add "$PARENT_DIR/${PROJECT_NAME}-${agent}" $SPRINT/$agent
done

# Install dependencies (customize for your stack)
# for agent in backend frontend infra services qa data; do
#   (cd "$PARENT_DIR/${PROJECT_NAME}-${agent}" && npm install)
# done

Post-Sprint Cleanup

for agent in backend frontend infra services qa data lead design; do
  git worktree remove "$PARENT_DIR/${PROJECT_NAME}-${agent}" 2>/dev/null
  git branch -d $SPRINT/$agent 2>/dev/null
done

Sprint Planning Source: [Your progress tracker]