Claude Code Plugin

Wire your agent into a full product team

For developers and small teams who build software with Claude Code and are tired of re-explaining how they work. addit-harness gives the agent a plan → verify → commit loop, fourteen specialist subagents, and a /dev-flow command that takes a change from idea to reviewed code — and stops for your approval before it writes any of it.

MIT licensed · Go · Java · TypeScript · Claude Code only

Install

claude code
/plugin marketplace add addit-digital/addit-harness
/plugin install addit-harness@addit
/addit-harness:setup
syncing agents/ · skills/ · rules/ · settings.json

Verify it worked

/help
✓ @addit-harness:code-reviewer and friends listed under Agents
3 commands, no clone required ● ready
PLAN VERIFY COMMIT THE ENGINEERING LOOP — ALWAYS ON
Before / After

Blank slate vs. harnessed

Same agent. The difference is what fires automatically, every session, on every machine.

LayerBlank slateWith addit-harness
Engineering processAd-hoc, re-decided every sessionPlan → verify → commit loop baked in
Legal complianceManual check, or skipped before shipping@saas-legal-advisor assesses every feature's legal impact
Language conventionsRe-pasted into context every sessionAuto-loaded per file type — Go, Java, TypeScript
Code review"Hey Claude, can you review this?"@code-reviewer enforces conventions with file:line citations
UX & designDescribe it and hope@ux-designer → @figma-designer → @frontend-architect pipeline
Feature buildHand-drive every Agent call yourself, every time/dev-flow — light, standard or deep effort, scripted design and review loops, and one approval gate before implementation
e2e/regression QAManual click-through before every release@qa-engineer — evidence-backed verification, web + mobile
New machineRedo everything by handThree commands
What's wired in

Seven connectors, one harness

Every layer of the build — idea to ship — has a specialized agent behind it.

01 · LOOP

Plan → verify → commit

Non-trivial work gets a written plan, small verifiable units, and real verification before it's called done — never an unverified "done."

02 · AGENTS

14 specialized subagents

Legal compliance, UX design, backend/frontend/cloud architecture, Go/Java/TS implementation, DevOps, and e2e/regression QA — each scoped, each with its own model tier.

03 · CONVENTIONS

Tiered language rules

Go, Java, and TypeScript conventions auto-load per file type — thin pointers at all times, deep references pulled in only for substantial work. Frontend work follows a contract that is checked with a line-count test. Where plugin and project disagree on where documents live, the plugin's layout wins.

04 · REVIEW

Convention-aware review

@code-reviewer checks correctness, security, and adherence to your vendored conventions — with file:line citations, not vague notes.

05 · CURATED

Vendored, not vibes

Assets are adopted from established sources and pinned at a commit — provenance tracked in AGENTS_SOURCES.md. Documents the agents write follow one protocol: short, describing the current state, diagrams kept, edited in place. The four architect and design agents' first turn went from about 33k to about 17k tokens in a controlled probe (3 runs each).

06 · LOCAL

Telemetry that stays on your machine

Off by default. If you turn it on, it logs metadata only, never sends it anywhere, and can build an offline report page. Publishing a summary as an Artifact happens only when you answer yes to that question.

07 · ORCHESTRATION

Effort that matches the change

/addit-harness:dev-flow scores each request into a light, standard or deep tier and shows you the result; you can move it one tier either way. Intake produces a one-page brief, the architect proposes its own alternatives before seeing your idea, QA runs once, and the design and review loops have round caps. Implementation never starts without your approval. Worst-case agent calls are capped per tier and asserted by tests (not measured on live runs).

How it works

One feature, six handoffs

A concrete build, start to ship — the subagents from "What's wired in," in the order they fire at the standard tier. /dev-flow runs this sequence for you, with a single approval gate before implementation starts. Follow a full worked example →

01

Investigate

@product-owner

02

Legal + UX

@saas-legal-advisor · @ux-designer

03

Architecture

@frontend-architect

04

Build

@backend-developer · @frontend-developer

05

Verify

@qa-engineer

06

Review

@code-reviewer

Get started

Three commands. Every session, wired.

Install from the Claude Code plugin marketplace — no clone, no shell script.