Compare
Up to three tools. The table shows the data as-is, without picking a “best”.
| Field | Backlog.md | dsh-git-graph | Superpowers |
|---|---|---|---|
| Platforms | Universal, Codex, Claude Code, Cursor | DeepSeek Harness | Claude Code, Codex, Cursor, OpenCode |
| Local support | Yes | Yes | Yes |
| Paid API | No | No | No |
| License | MIT | Apache-2.0 | MIT |
| Stars | 7130 | 9384 | 304147 |
| Last activity | — | September 25, 2026 | — |
| Install complexity | Easy — npm, Bun, Homebrew, or Nix | سهل / Easy | — |
| Category | Multi-Agent, Git, Workflow | Git, Workflow, UI | Code Review, Multi-Agent, Testing, Workflow |
| Best use | Best for an individual developer or small team using coding agents and wanting to review the specification and plan before code. It keeps tasks, acceptance criteria, and decisions inside the project and exposes them through CLI, a local browser, or MCP. It is not a replacement for a centralized enterprise SaaS board with organization-wide permissions and reporting. | Best for a developer running several DSH sessions against one repository who wants visible branch context, history, and worktree creation in the UI. It adds session isolation and readable branch-switch guards. It may be excessive for one small change on one branch or for environments that prohibit outbound telemetry. | Best for a developer or project owner working on a substantial feature or a difficult bug. It helps clarify requirements, approve a plan, and inspect tests and file changes. Its value is a visible path from decision to verification. A small text edit may not need the full workflow. |