harness-korean

Harness — The Team-Architecture Factory for Claude Code

English | 한국어 | 日本語

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.

Overview

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.

Category — Where Harness Sits

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

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.

Star History

Key Features

• Agent Team Design — 6 architectural patterns: Pipeline, Fan-out/Fan-in, Expert Pool, Producer-Reviewer, Supervisor, and Hierarchical Delegation
• Skill Generation — Auto-generates skills with Progressive Disclosure for efficient context management
• Orchestration — Inter-agent data passing, error handling, and team coordination protocols
• Validation — Trigger verification, dry-run testing, and with-skill vs without-skill comparison tests

Harness Evolution Mechanism

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.