todoslisted

# Todos Skill Tracks implementation todos per project AND captures the relational project intelligence around them. Each project has two stores — a **task board** and a **project brain** — plus local long-form files. Where the board and brain physically live depends on the active backend (see **Backends & the write path** below): - **Task board** — tasks and phases. (`.claude/todos.json` under the `json` backend; a Postgres row-set under `pg`.) - **Project brain** — stakeholders, feedback, decisions, contradictions, business rules, scope changes, architecture notes, **per-task plans + their planning Q&A**. (`.claude/brain.db` SQLite under `json`; Postgres tables under `pg`.) - `.claude/{docs,notes,diagrams}/` — long-form markdown and Mermaid diagrams (always local files, referenced from the brain). Commands never hand-edit any of this directly — every read/write goes through the backend-aware CLIs `board-cli`/`brain-cli` (or the equivalent MCP tools, where available), so the same command works unchanged regardless of which backend is live. Throughout this doc and the command prompts, `todos.json`/`brain.db` are shorthand for the board/brain **stores** — not a claim that a local file is authoritative. A local Bun server at `http://localhost:5757` reads every tracked project and renders an aggregated newspaper-style dashboard with Today / Project / Activity / Brain / Brief / **Week** / **Hold** / Studio tabs. ## Backends & the write path `lib/backend.ts`'s `resolveBackend