A
licenseNot graded
qualityB
maintenanceEnables AI coding agents to file and track issues, plan epics with steps, comment as they work, and hand decisions back to the user through a local Markdown- and YAML-backed issue tracker.
MIT
brindley
by duckAsteroid
Related Servers
Alternatives to brindley
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables AI coding agents to register, self-assign and coordinate tasks, track progress, review work, and manage GitHub Projects v2 with AI-powered PRD generation, sprint planning, issue triage, and PRD-to-issues pipelines backed entirely by GitHub-native storage.35 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables AI agents and human managers to orchestrate GitHub-based project work by self-assigning tasks, coordinating swarms, tracking token budgets, generating PRDs, planning sprints, triaging issues, and materializing tasks as GitHub issues, milestones, and project views.35 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables AI coding agents to register, claim tasks atomically, coordinate via heartbeats, review each other's work, enforce token budgets, and ship code using GitHub Projects v2 as the backing store. It also gives humans AI-powered PRD generation, sprint planning, issue triage, and roadmap creation without external infrastructure.35 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables AI coding agents and teams to turn GitHub Projects v2 into an autonomous task substrate for registering, claiming, tracking, reviewing, and completing work, while also supporting AI-powered PRD generation, sprint planning, issue triage, roadmap creation, GitHub Actions/releases/branches, and MCP resources/prompts.35 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables AI coding agents to self-assign and coordinate tasks, track progress and token budgets, and automate GitHub project workflows such as PRD-to-issues pipelines, sprint planning, triage, reviews, and releases.35 npmMIT
TDQS
B3.4/5.0
Scored across 35 tools
Disambiguation4/5
Most tools target a distinct resource+action: collections, initiatives, questions, dependencies, milestones, tags and docs each get their own verbs, and descriptions pre-empt common confusions (update says 'to change a recorded status, use set_status'; fix says 'padding is fixed by repad, numbers by renumber'). Residual overlap exists in the repair cluster (validate/fix/repad/renumber/tidy), the readiness pair (ready lists workable initiatives vs check_ready gates a single one) and update vs batch_update, but these are distinguishable with care.
Naming Consistency3/5
There is an implicit split — bare-noun query tools (collections, tags, milestones, questions, fields, graph, report) and bare-verb mutation tools (create, update, get, complete, fix, tidy, repad, renumber) — alongside consistent verb_noun tools (set_status, add_question, check_ready, create_collection). This is readable and partly intentional, but it is not one predictable pattern: 'list' lacks a noun while 'collections' has no verb, and create/update sit next to create_collection/update_collection style names.
Tool Count2/5
At 35 tools the surface is heavy for a ticket/initiative server; an agent must scan a long catalogue to find the right verb. Many are individually justified by the git-aware domain, but several clusters (fix/repad/renumber/tidy, validate/check_docs/check_ready) could be consolidated into fewer tools with mode parameters.
Completeness4/5
Coverage of the stated domain is strong: full initiative lifecycle (create/get/list/update/batch_update/set_status/complete), questions (add/split/resolve/next/list), dependencies and graph, collections management, milestones, tags, validation and repair, docs linting, briefs, reports and worktree switching. Minor gaps: no way to delete/remove an initiative (mitigated by abandoned/superseded statuses), no tool to create milestones or arbitrary docs, and no explicit search beyond list filters.
Maintenance
ActivityMaintained
ResponsivenessResponsive