Sprint and Kanban

Overview

The manager owns the kanban. The user and manager co-plan priorities. Sprint state is tracked in SPRINT.md at the project root (or path configured in project-config.md).

SPRINT.md Format

YAML frontmatter with kanban state, followed by optional notes.

---
sprint:
  id: 1
  start: 2026-03-28
  goal: "Implement pivot strategy for symbolic factorization"
  status: active    # active | completed | halted

backlog:
  - id: T001
    summary: "Research pivot stability bounds"
    card: null              # no card yet (research phase)
    agent: res-dev
    status: done
    branch: research/pivot_stability

  - id: T002
    summary: "Design pivot integration point"
    card: S01
    agent: arch-dev
    status: done
    branch: feature/S01_pivot_strategy

  - id: T003
    summary: "Implement pivot strategy"
    card: S01
    agent: code-dev
    status: doing
    branch: feature/S01_pivot_strategy

  - id: T004
    summary: "Review pivot implementation"
    card: S01
    agent: code-rev
    status: todo
    branch: feature/S01_pivot_strategy

  - id: T005
    summary: "Update S01 card and Doxygen"
    card: S01
    agent: kb-dev
    status: todo
    branch: kb/S01_card_update

  - id: T006
    summary: "Full regression test"
    card: S01
    agent: bench
    status: todo
    branch: null

decisions:
  - date: 2026-03-28
    decision: "Use Markowitz pivoting with threshold 0.1"
    context: "Research showed threshold < 0.01 causes instability"

halts: []
---

## Notes

{Free-form notes, discussion points, or context for the sprint}

Kanban States

Status	Meaning
todo	In backlog, not started
doing	Currently being worked on (one at a time)
review	Dev complete, reviewer working
done	Task complete, reviewer approved
blocked	Waiting on user decision or external dependency

One doing at a time

Sequential execution. No parallel work.

Task IDs

Sequential within a sprint: T001, T002, T003, ...

Tasks reference card IDs when applicable (card field). Research tasks may have card: null since idea cards don't have IDs yet.

Backlog

Items not assigned to the current sprint live at the bottom of the backlog with status: todo. The user and manager promote items to the sprint during planning.

Manager Responsibilities

The manager maintains SPRINT.md:

When	Action
Planning session	Create/update sprint with user
Agent completes task	Move task to done, update branch
User gates phase	Move next task to doing
HALT declared	Set sprint status to halted, log in halts
Sprint complete	Set sprint status to completed, archive

Standup References Sprint

The daily standup reads SPRINT.md to produce the Done/Doing/Blocked sections. See the manager skill for the standup format.