Skip to content

Harness Interface

github-actions[bot] edited this page Jun 11, 2026 · 3 revisions

Harness interface ↔ Agent M

The seam between this toolkit and the sibling agentm harness — what each owns, and how they compose without depending on each other.

agentm owns the phase-gated workflow (/plan · /work · /review · /release · /bugfix) and the canonical phase specs. crickets owns the customizations — skills, agents, hooks, and the rest — that ride on top. Neither requires the other to exist: the harness suggests crickets primitives (e.g. ship-release) as graceful-skip steps, and crickets primitives enhance the harness phases when both are installed. The split was made in crickets v2.0.0.

Cross-references:

See also

Architecture · Explanation · Home

Clone this wiki locally