Plan work as Markdown in your git repo. Settle every open question with your AI agent, then hand it over to build — with an MCP server that keeps it all straight.
📖 Documentation: duckasteroid.github.io/brindley — getting started, concepts, ,
Potencialize seu agente
O comando do próprio publicador. Não é um endpoint do PlugMCP.
Host a copy with our keys and logs.
npx -y [email protected]O Claude Code não tem link de instalação para um comando local. Copie o comando abaixo e execute-o em um terminal.
claude mcp add brindley -- npx -y brindley@3.0.0Execute em um terminal.
{ "mcpServers": { "brindley": { "command": "npx", "args": [ "-y", "[email protected]" ] } }}claude_desktop_config.json
URL remota ou um comando na sua máquina? Como as duas instalações diferem
Rodar no PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
AbrirDo publicador
Plan work as Markdown in your git repo. Settle every open question with your AI agent, then hand it over to build — with an MCP server that keeps it all straight.
📖 Documentation: duckasteroid.github.io/brindley — getting started, concepts, ,
Design fully before anyone digs — in-repo Markdown initiatives for AI-agent workflows, plus an MCP server
For Claude Code, install the plugin once and it works in every repo (Node 20+ and git):
claude plugin install brindley --marketplace duckAsteroid/brindley
It brings the MCP server at a pinned version, the workflows as skills (/brindley:design-review,
/brindley:implement, /brindley:spike, /brindley:triage) and an implementer agent. Allow its
tools with the permission rule mcp__plugin_brindley_brindley.
Then ask your agent to "make docs/plans a collection". For the people outside the team,
npx -y brindley@latest report writes a one-page progress report from the collections and their
git history (example). Without the plugin
(claude mcp add -s user brindley -- npx -y brindley@latest) and for other MCP clients (opencode,
…), see getting started.
npm test # unit + MCP-level tests
npm run build # stamps the version, compiles to dist/
npm run version:explain # how the current version is computed
cd site && npm install && npm run dev # the documentation site
The version comes from git: the last vX.Y.Z tag, bumped by the Conventional Commits since it
(feat → minor, fix/perf → patch, ! → major), with -SNAPSHOT off-tag — the same rules as
gradle-versioning. Release with
npm run release:prepare, which commits the next version into the Claude Code plugin (plugin/),
then tag and push — git tag -a v1.0.0 -m "<highlights>" && git push origin main v1.0.0 — and the
Release workflow checks the plugin names the tag's version, validates it, tests, publishes to npm
(with provenance) and creates a GitHub Release. Its notes, and the site's
Releases page, come from
node scripts/changelog.mjs: the annotated tag's message as highlights (optional — a plain tag
gives none), then the feat, fix, perf and breaking commits since the previous release.
Design documents: FORMAT.md (the file format) and MCP-SERVER.md
(the server). Documentation pages live in site/ and publish to GitHub Pages on push.
MIT © 2026 Chris Senior
Design fully before anyone digs — in-repo Markdown initiatives for AI-agent workflows, plus an MCP server
{ "mcpServers": { "brindley": { "command": "npx", "args": [ "-y", "[email protected]" ] } }}Ferramentas
Ainda não há lista de ferramentas. Servidores remotos recebem uma após a primeira verificação de saúde.
Perguntas frequentes
Copie nesta página a configuração stdio para Cursor, Claude Desktop, Claude Code ou VS Code. Ela usa a instalação do publicador, não um proxy do PlugMCP.
Este registro não lista nenhuma variável de ambiente obrigatória.
Brindley roda localmente via stdio.
Última verificação: 2026-11-13. Design fully before anyone digs — in-repo Markdown initiatives for AI-agent workflows, plus an MCP server