The build loop
The agent reads the live board, picks up the story marked In Progress, does the work, opens a PR — and moves the ticket only when it actually ships. The board drives the work; the work updates the board.
The plan is the contract.
tada is a methodology for building products with agents, built around a shared plan board. The board is where a human and a coding agent agree on what to build — the agent reads and edits it through MCP tools, and a set of skills turn it into repeatable loops.
Idea
✨ Offline board cache
🏗️ Split staging environment
Planned
🐛 Tag filter drops on reload
In Progress
✨ Marketing site at the apex
Done
🧹 Drop the normalize-on-read shim
✨ Per-story optimistic concurrency
Two loops
The board and MCP let an agent edit a plan. The skills are what make tada a way of working.
The audit → board loop
A sweep of the whole codebase emits findings with durable ids, tracked across runs so re-running never re-files what's already on the board. You file the ones worth doing, and they feed straight into the build loop.