redker56/auto-harness
11 stars · Last commit 2026-04-06
Run Claude Code like a specialist software team: planning, implementation, QA, fix/retest loops, and durable .harness state for long-running project delivery.
README preview
# Auto-Harness [English](README.md) | [中文](README.zh-CN.md) This plugin is based on Anthropic's article, [Harness design for long-running application development](https://www.anthropic.com/engineering/harness-design-long-running-apps). Auto-Harness lets you run Claude Code like a small, specialized software team instead of a single endless chat. Give it a brief, and it drives planning, implementation, QA, fix/retest, and final reporting through a durable `Planner -> Generator -> Evaluator` workflow backed by `.harness/`. ## At A Glance - Turn one product brief into a staffed-looking delivery workflow inside Claude Code - Split planning, implementation, QA, and fix/retest into specialist roles instead of one overloaded assistant - Keep durable `.harness/` artifacts so multi-day work survives restart, compaction, and handoff - Review each sprint contract before code is written so implementation stays pointed at a real target - Gate QA, retest, and final reporting with explicit reviewer agents before state advances ## What Problem It Solves - Long tasks collapse when planning, implementation, and QA all happen in one thread - Multi-day project work needs durable state, not just chat history and wishful thinking