Batch 12 — PM / Ticketing / Backlog Tools

Roster (10)

slug	stars	distribution	cli_binary	local_ui	orchestration	multi_model	tier
backlog-md	5622	npm-package	`backlog`	web-dashboard (port 6420)	task-decomp-tree	no	A
ccpm	8146	skill-pack	none	none (GitHub Issues)	parallel-fan-out	no	A
andai	5	standalone-repo	`andai`	web-dashboard (Redmine, port 3000)	sequential	yes	A
ai-ticket-jmike	33	standalone-repo	none	none	sequential	no	B
sprintcore	16	cli-tool	`sprintcore`	none	none	yes (pipeline)	B
reqtext	0	npm-package	`reqt`	terminal-tui	none	no	B
tracer-issue-tracker	20	cli-tool	`tracer`	none	task-decomp-tree	no	A
boomerang-tasks	unknown	unknown	unknown	unknown	unknown	unknown	C
taskval	unknown	unknown	unknown	unknown	unknown	unknown	C
desktop-commander	unknown	unknown	unknown	unknown	unknown	unknown	C

Intra-batch Patterns

The batch divides cleanly into three groups. The first group (backlog-md, ccpm, tracer, andai) are genuine multi-agent-aware task trackers with explicit dependency management and parallel agent support. The second group (sprintcore, reqtext, ai-ticket-jmike) are pre-execution tools — they generate work artifacts (stories, requirements, tickets) but don't manage execution. The third group (boomerang-tasks, taskval, desktop-commander) are Reddit-referenced patterns with insufficient standalone repos. A notable pattern: every tool except ccpm stores task state in local files rather than a database, reflecting the "git-native" philosophy of the AI coding agent ecosystem. GitHub Issues as the coordination layer (used by ccpm and ai-ticket-jmike) is the outlier approach — most tools prefer local file stores that travel with the repo.

Most Interesting Finds

backlog-md (5622 stars): The standout in the batch — the only framework with a full web Kanban dashboard synced to per-task markdown files AND an MCP server AND cross-tool support for Claude Code/Codex/Gemini/Kiro/Cursor. The onStatusChange callback enabling "when task reaches In Progress, auto-launch an agent" is a novel event-driven integration hook. Its 38 contributors and 5622 stars suggest real production adoption.
andai (5 stars): The most architecturally ambitious tool in the batch — a self-hosted Devin equivalent using Redmine + MariaDB + Aider + YAML-configurable state machines with per-step multi-model routing. The remember: true flag for accumulating context across workflow steps is a sophisticated prompt-chaining mechanism not found in other frameworks.

Items Written as Tier C

boomerang-tasks — No standalone GitHub repo found. Reddit references describe an orchestrator-subagent dispatch pattern in Roo Code/Roo Commander, not an independent framework. Likely refers to Roo Code's built-in boomerang mode.
taskval — No GitHub repo found via search. Reddit references describe a "refuse vague tasks" validation pattern; may be an informal convention or lost Reddit post rather than a published tool.
desktop-commander — Ambiguous reference; likely wonderwhy-er/DesktopCommanderMCP (a general MCP server for terminal/file access) used in a PRD workflow, not a dedicated PM framework.

Cross-references Discovered

ccpm explicitly supports the agentskills.io skill format, connecting it to the broader batch-11 (skill marketplaces) ecosystem
backlog-md ships both MCP and CLI integration paths — architecturally bridges the MCP-anchored toolserver archetype (taskmaster-ai seed) and the markdown-scaffold archetype (claude-conductor seed)
andai uses Aider (not Claude Code/Codex), connecting it to the aider seed framework analyzed in earlier phases
tracer-issue-tracker shares the git-auto-discovery pattern with git itself; its JSONL format is structurally similar to the event log patterns in andai's Redmine comments
The "GitHub Issues as task store" pattern (ccpm, ai-ticket-jmike) is the only approach in this batch using a remote team-visible store rather than repo-local files — a meaningful architectural fork vs taskmaster-ai's local tasks.json