Harness Lets Claude Design Its Own Agent Team
revfactory/harness is the next layer up from skill packs. Tell Claude Code 'build a harness for this project,' and it produces the agents, the skills, and the orchestration glue for your specific domain — agent definitions in .claude/agents, skill files in .claude/skills, and one of six prebuilt architectural patterns (pipeline, fan-out/fan-in, expert pool, producer-reviewer, supervisor, hierarchical delegation) wiring them together. 4.2k stars, trending, MIT-style install via /plugin marketplace add revfactory/harness.
The story is the trajectory. A year ago people hand-wrote one skill at a time. A month ago Anthropic shipped the official plugins directory and Every shipped Compound Engineering — the SHELVES with curated packs on them. Harness is the next stop: a meta-skill that says give me your domain and I will design the team. There is a companion repo, harness-100, with 100 ready-made packs across 10 domains, 1,808 markdown files in two languages.
Author-reported A/B testing across 15 tasks claims +60% quality and -32% variance versus hand-built setups, with the honest caveat that third-party replications are pending. Take that as a flag, not a fact. What matters is the layer it occupies — the GitHub README calls it L3 Meta-Factory, sitting above Archon (runtime) and ECC (cross-harness standardization).
The pattern to watch: when designing the team becomes a one-liner, the question moves up one rung. Stop asking 'which agent should I write' and start asking 'which domain shape am I in.' Pipeline vs hierarchical is a design decision; harness turns it into a tag you pick.
Repo: https://github.com/revfactory/harness
← Back to all articles
The story is the trajectory. A year ago people hand-wrote one skill at a time. A month ago Anthropic shipped the official plugins directory and Every shipped Compound Engineering — the SHELVES with curated packs on them. Harness is the next stop: a meta-skill that says give me your domain and I will design the team. There is a companion repo, harness-100, with 100 ready-made packs across 10 domains, 1,808 markdown files in two languages.
Author-reported A/B testing across 15 tasks claims +60% quality and -32% variance versus hand-built setups, with the honest caveat that third-party replications are pending. Take that as a flag, not a fact. What matters is the layer it occupies — the GitHub README calls it L3 Meta-Factory, sitting above Archon (runtime) and ECC (cross-harness standardization).
The pattern to watch: when designing the team becomes a one-liner, the question moves up one rung. Stop asking 'which agent should I write' and start asking 'which domain shape am I in.' Pipeline vs hierarchical is a design decision; harness turns it into a tag you pick.
Repo: https://github.com/revfactory/harness
Comments