by revfactory
A meta-skill that designs domain-specific agent teams, defines specialized agents, and generates the skills they use.
# Add to your Claude Code skills
git clone https://github.com/revfactory/harnessLast scanned: 4/22/2026
{
"issues": [],
"status": "PASSED",
"scannedAt": "2026-04-22T06:02:12.991Z",
"semgrepRan": false,
"npmAuditRan": true,
"pipAuditRan": true
}Harness is a team-architecture factory for Claude Code. Say "build a harness for this project" (English) or "하네스 구성해줘" (한국어) or "ハーネスを構成して" (日本語), and the plugin turns your domain description into an agent team and the skills they use — picked from six pre-defined team-architecture patterns.
Harness leverages Claude Code's agent team system to decompose complex tasks into coordinated teams of specialized agents. Say "build a harness for this project" and it automatically generates agent definitions (.claude/agents/) and skills (.claude/skills/) tailored to your domain.
Harness lives at the L3 Meta-Factory layer of the Claude Code ecosystem — the layer that generates other harnesses rather than being one. Inside L3, we pick a specific sub-layer: Team-Architecture Factory.
| Layer | What it does | Neighbors we coexist with | |-------|--------------|---------------------------| | L3 — Meta-Factory / Team-Architecture Factory (us) | Domain sentence → agent team + skills, via 6 pre-defined team patterns | — | | L3 — Meta-Factory / Runtime-Configuration Factory | Deterministic, repeatable runtime configurations | coleam00/Archon | | L3 — Meta-Factory / Codex Runtime Port | Same concept, Codex runtime | SaehwanPark/meta-harness | | L2 — Cross-Harness Workflow | Standardize skills/rules/hooks across multiple harnesses | affaan-m/ECC |
No comments yet. Be the first to share your thoughts!
Archon generates deterministic runtime configurations. Harness generates team architectures (pipeline, fan-out/fan-in, expert pool, producer-reviewer, supervisor, hierarchical delegation) plus the skills agents use. Different sub-layers of the same L3. Pick Archon for runtime determinism, Harness for team architecture, or combine them.
The harness evolution mechanism feeds deltas (what worked / what didn't) back into the factory, so the next generation is measurably better. When a generated harness is used in a real project, the /harness:evolve skill captures the delta between the initial architecture and the shipped one, and feeds it back into the factory so the next generation for a similar domain starts closer to the shipped state.
Initial harness ──▶ Real project use ──▶ Shipped harness
│
▼ (delta capture via /harness:evolve)
┌───────────────┐
│ Factory │◀── better next-gen draft
└───────────────┘
We call this the Harness Evolution Mechanism (KR: 하네스 진화 메커니즘; JA: ハーネス進化メカニズム).
Phase 1: Domain Analysis
↓
Phase 2: Team Architecture Design (Agent Teams vs Subagents)
↓
Phase 3: Agent Definition Generation (.claude/agents/)
↓
Phase 4: Skill Generation (.claude/skills/)
↓
Phase 5: Integration & Orchestration
↓
Phase 6: Validation & Testing
/plugin marketplace add revfactory/harness
/plugin install harness@harness
# Copy the skills directory to ~/.claude/skills/harness/
cp -r skills/harness ~/.claude/skills/harness
harness/
├── .claude-plugin/
│ └── plugin.json # Plugin manifest
├── skills/
│ └── harness/
│ ├── SKILL.md # Main skill definition (6-Phase workflow)
│ └── references/
│ ├── agent-design-patterns.md # 6 architectural patterns
│ ├── orchestrator-template.md # Team/subagent orchestrator templates
│ ├── team-examples.md # 5 real-world team configurations
│ ├── skill-writing-guide.md # Skill authoring guide
│ ├── skill-testing-guide.md # Testing & evaluation methodology
│ └── qa-agent-guide.md # QA agent integration guide
└── README.md
Trigger in Claude Code with prompts like:
Build a harness for this project
Design an agent team for this domain
Set up a harness
| Mode | Description | Recommended For | |------|-------------|-----------------| | Agent Teams (default) | TeamCreate + SendMessage + TaskCreate | 2+ agents requiring collaboration | | Subagents | Direct Agent tool invocation | One-off tasks, no inter-agent communication needed |
| Pattern | Description | |---------|-------------| | Pipeline | Sequential dependent tasks | | Fan-out/Fan-in | Parallel independent tasks | | Expert Pool | Context-dependent selective invocation | | Producer-Reviewer | Generation followed by quality review | | Supervisor | Central agent with dynamic task distribution | | Hierarchical Delegation | Top-down recursive delegation |
Files generated by Harness:
your-project/
├── .claude/
│ ├── agents/ # Agent definition files
│ │ ├── analyst.md
│ │ ├── builder.md
│ │ └── qa.md
│ └── skills/ # Skill files
│ ├── analyze/
│ │ └── SKILL.md
│ └── build/
│ ├── SKILL.md
│ └── references/
Copy any prompt below into Claude Code after installing Harness:
Deep Research
Build a harness for deep research. I need an agent team that can investigate
any topic from multiple angles — web search, academic sources, community
sentiment — then cross-validate findings and produce a comprehensive report.
Website Development
Build a harness for full-stack website development. The team should handle
design, frontend (React/Next.js), backend (API), and QA testing in a
coordinated pipeline from wireframe to deployment.
Webtoon / Comic Production
Build a harness for webtoon episode production. I need agents for story
writing, character design prompts, panel layout planning, and dialogue
editing. They should review each other's work for style consistency.
YouTube Content Planning
Build a harness for YouTube content creation. The team should research
trending topics, write scripts, optimize titles/tags for SEO, and plan
thumbnail concepts — all coordinated by a supervisor agent.
Code Review & Refactoring
Build a harness for comprehensive code review. I want parallel agents
checking architecture, security vulnerabilities, performance bottlenecks,
and code style — then merging all findings into a single report.
Technical Documentation
Build a harness that generates API documentation from this codebase.
Agents should analyze endpoints, write descriptions, generate usage
examples, and review for completeness.
Data Pipeline Design
Build a harness for designing data pipelines. I need agents for schema
design, ETL logic, data validation rules, and monitoring setup that
delegate sub-tasks hierarchically.
Marketing Campaign
Build a harness for marketing campaign creation. The team should research
the target market, write ad copy, design visual concepts, and set up
A/B test plans with iterative quality review.
Harness is not alone in the Claude Code / agent-framework ecosystem. The following repos live in adjacent layers; each is described in