“I need to clear a backlog”
Start from a use case. Each one names the team to build, the order of the steps, and what the board looks like when it is done. Use these if you know the outcome you want but not the mechanism.
6 matches across 34 indexed pages and answers.
Most people arrive with one of three questions. Pick the one that matches yours and the rest of the site follows from there.
Start from a use case. Each one names the team to build, the order of the steps, and what the board looks like when it is done. Use these if you know the outcome you want but not the mechanism.
Start from a feature. Each page explains the problem it removes, how it behaves in the app, and which use cases depend on it. Use these if you already know what capability you are shopping for.
Start from a comparison. Each one says plainly when the other tool is the better pick, and when it is not. Use these if you already run something and want to know what changes.
How this search works. The index is built at compile time from the same data that renders the pages, so a result can never point at something that does not exist. Matching runs on the server, which means results render without JavaScript and the URL you land on is shareable. Nothing you type is sent anywhere or stored — the query lives in the address bar and nowhere else.
No hidden pages, no dead ends. Every route below is server-rendered and linked.
Features
Use cases
Every path on this site ends in the same place: a board with agents on it.