@chaafoo/anchored-mcp

Configure long, autonomous AI runs — plan → refine → build → wrap, on epics or tasks — with anchored evidence at every step.

Shape each step of your work — your tests, commits, gates, your tools — and anchor evidence to every implementation. With anchored, an AI can run for hours and you still trust the result: nothing reaches done without the proof to back it.

Same lifecycle at every scale — epic ▸ task ▸ phase. CLI-only, zero-install plugin, no MCP.

What ships here

Package	Distributed as	Role
plugin/	Claude Code marketplace plugin (anchored)	Skills, agents, references — what users install. Bundles its own CLI; zero setup.
core/	Bundled into the plugin	The factory engine + bundled anchored CLI — schema, state machine, atomic writes, and the evidence invariant.

The plugin ships the user-facing skills (/a:plan · /a:refine · /a:build · /a:wrap · /a:setup) and agents; the core package ships the deterministic engine they drive over the CLI. No MCP — one transport, the anchored CLI over Bash, identical in the main session and in subagents/headless.

User-facing docs: plugin/README.md · engine internals: core/README.md.

Quick start

In Claude Code:

/plugin marketplace add chafoo/anchored
/plugin install a@anchored

Not on the official Claude Code marketplace yet — this adds the GitHub repo (chafoo/anchored) as a marketplace source. An official listing is the next step.

Then in any project:

/a:plan <describe an epic, a task, or a phase>   # the tier is an argument of plan
/a:refine <slug>                                  # ground the plan + Q&A walk + gates
/a:build <slug>                                   # implement + verify, phase by phase
/a:wrap <slug>                                     # review + summary (+ epic roll-up)

The CLI ships inside the plugin — Claude Code puts plugin/bin/ on PATH for you, in the main session and in subagents. No npm i -g, no MCP setup.

Docs

The docs hub is docs/:

• CLI API — every anchored <tier> <verb> [slug] command and the /a:* skills
• Tier portraits — epic · task · phase, and what each one is for
• Lifecycle stages — setup · plan · refine · build · wrap

Contribute

git clone https://github.com/chafoo/anchored
cd anchored/core
bun install
bun run test     # the spec-coverage gate + unit + e2e + int suites
bun run build    # tsc → dist/ (Node-compatible artifact)

The non-negotiable principles are in CLAUDE.md.

Status

Pre-1.0 — the v3 architecture is built and dogfood-validated; APIs may still shift. Tier model epic ▸ task ▸ phase, plugin namespace a. Not yet on the official Claude Code marketplace — install via the GitHub repo as a source (see Quick start). The engine also lives in core/ as a standalone package (not yet published); the plugin bundles the CLI, so users never need it.

License

MIT — see LICENSE.

---

Built by @chafoo.