sprint-plannerlisted

# Sprint planner Convert `docs/11-backlog.md` + `docs/22-impl-spec-*.md` into `docs/30-sprint-plan.md` and `docs/31-board.md`. ## Procedure 1. **Read** the backlog and impl specs. Note ticket dependencies — if APP-002 needs APP-001's auth module, that's a dependency. 2. **Sprint goal** — one sentence at the top of `docs/30-sprint-plan.md`. 3. **Capacity** — default 3 developer agents (iOS, Android, optional Backend), 1 code-reviewer, 1 qa-engineer, 1 ux-architect, 1 product-designer. Tune to project scope. 4. **Assign for parallelism** — group tickets so each developer has independent work to start with. Stack dependent work behind it. ``` Track A (ios-developer) : APP-001 → APP-004 → APP-007 Track B (android-dev) : APP-002 → APP-005 → APP-008 Track C (backend-dev) : APP-003 → APP-006 Continuous: code-reviewer, qa-engineer, ux-architect + product-designer (early) ``` 5. **Board — create tickets through the CLI. Never hand-write the table.** `docs/31-board.md` is a **generated view**. The source of truth is the append-only event log `docs/31-board-events.jsonl`, and `scripts/board.mjs` is its only writer. A ticket is created by: ```bash node "${CLAUDE_PLUGIN_ROOT}/scripts/board.mjs" add APP-001 \ --title "Core todo store" --feature F-001 --owner android-developer \ --depends APP-000 --estimate M --spec "prd#F-001 + arch§3" \ --acceptance "Given the list, When I submit non-empty text, Then it appears at the top" \