[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"project-75055":3},{"id":4,"name":5,"fullName":6,"owner":7,"repo":5,"description":8,"homepage":9,"htmlUrl":10,"language":11,"languages":10,"totalLinesOfCode":10,"stars":12,"forks":13,"watchers":14,"openIssues":15,"contributorsCount":16,"subscribersCount":16,"size":16,"stars1d":17,"stars7d":18,"stars30d":19,"stars90d":16,"forks30d":16,"starsTrendScore":20,"compositeScore":21,"rankGlobal":10,"rankLanguage":10,"license":22,"archived":23,"fork":23,"defaultBranch":24,"hasWiki":25,"hasPages":25,"topics":26,"createdAt":10,"pushedAt":10,"updatedAt":30,"readmeContent":31,"aiSummary":32,"trendingCount":16,"starSnapshotCount":16,"syncStatus":33,"lastSyncTime":34,"discoverSource":35},75055,"harness","revfactory\u002Fharness","revfactory","A meta-skill that designs domain-specific agent teams, defines specialized agents, and generates the skills they use.","https:\u002F\u002Frevfactory.github.io\u002Fharness\u002F",null,"HTML",6738,922,41,3,0,507,2205,3469,1521,39.9,"Apache License 2.0",false,"main",true,[27,28,5,29],"claude-code","claude-code-plugin","harness-engineering","2026-06-12 02:03:31","\u003Cp align=\"center\">\n  \u003Cimg src=\"harness_banner.png\" alt=\"Harness Banner\" width=\"600\">\n\u003C\u002Fp>\n\n\u003Cp align=\"center\">\n  \u003Cimg src=\"https:\u002F\u002Fimg.shields.io\u002Fbadge\u002FVersion-1.2.0-brightgreen.svg\" alt=\"Version\">\n  \u003Ca href=\"LICENSE\">\u003Cimg src=\"https:\u002F\u002Fimg.shields.io\u002Fbadge\u002FLicense-Apache_2.0-blue.svg\" alt=\"License\">\u003C\u002Fa>\n  \u003Cimg src=\"https:\u002F\u002Fimg.shields.io\u002Fbadge\u002FClaude_Code-Plugin-purple.svg\" alt=\"Claude Code Plugin\">\n  \u003Cimg src=\"https:\u002F\u002Fimg.shields.io\u002Fbadge\u002FPatterns-6_Architectures-orange.svg\" alt=\"6 Architecture Patterns\">\n  \u003Cimg src=\"https:\u002F\u002Fimg.shields.io\u002Fbadge\u002FMode-Agent_Teams-green.svg\" alt=\"Agent Teams\">\n  \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Frevfactory\u002Fharness\u002Fstargazers\">\u003Cimg src=\"https:\u002F\u002Fimg.shields.io\u002Fgithub\u002Fstars\u002Frevfactory\u002Fharness?style=social\" alt=\"GitHub Stars\">\u003C\u002Fa>\n\u003C\u002Fp>\n\n\u003Cp align=\"center\">\n  \u003Ca href=\"#category--where-harness-sits\">\u003Cimg src=\"https:\u002F\u002Fimg.shields.io\u002Fbadge\u002FLayer-L3%20Meta--Factory-orange\" alt=\"Layer\">\u003C\u002Fa>\n  \u003Ca href=\"#category--where-harness-sits\">\u003Cimg src=\"https:\u002F\u002Fimg.shields.io\u002Fbadge\u002FSub--layer-Team--Architecture%20Factory-teal\" alt=\"Sub-layer\">\u003C\u002Fa>\n  \u003Ca href=\"#\">\u003Cimg src=\"https:\u002F\u002Fimg.shields.io\u002Fbadge\u002FREADME-EN%20%7C%20KO%20%7C%20JA-lightgrey\" alt=\"i18n\">\u003C\u002Fa>\n\u003C\u002Fp>\n\n# Harness — The Team-Architecture Factory for Claude Code\n\n**English** | [한국어](README_KO.md) | [日本語](README_JA.md)\n\n> **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.\n\n## Overview\n\nHarness 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\u002Fagents\u002F`) and skills (`.claude\u002Fskills\u002F`) tailored to your domain.\n\n## Category — Where Harness Sits\n\nHarness 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**.\n\n| Layer | What it does | Neighbors we coexist with |\n|-------|--------------|---------------------------|\n| **L3 — Meta-Factory \u002F Team-Architecture Factory** (us) | Domain sentence → agent team + skills, via 6 pre-defined team patterns | — |\n| L3 — Meta-Factory \u002F Runtime-Configuration Factory | Deterministic, repeatable runtime configurations | [coleam00\u002FArchon](https:\u002F\u002Fgithub.com\u002Fcoleam00\u002FArchon) |\n| L3 — Meta-Factory \u002F Codex Runtime Port | Same concept, Codex runtime | [SaehwanPark\u002Fmeta-harness](https:\u002F\u002Fgithub.com\u002FSaehwanPark\u002Fmeta-harness) |\n| L2 — Cross-Harness Workflow | Standardize skills\u002Frules\u002Fhooks across multiple harnesses | [affaan-m\u002FECC](https:\u002F\u002Fgithub.com\u002Faffaan-m\u002Feverything-claude-code) |\n\n> Archon generates deterministic runtime configurations. Harness generates team architectures (pipeline, fan-out\u002Ffan-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.\n\n## Star History\n\n\u003Ca href=\"https:\u002F\u002Fwww.star-history.com\u002F?repos=revfactory%2Fharness&type=date&legend=top-left\">\n \u003Cpicture>\n   \u003Csource media=\"(prefers-color-scheme: dark)\" srcset=\"https:\u002F\u002Fapi.star-history.com\u002Fchart?repos=revfactory\u002Fharness&type=date&theme=dark&legend=top-left\" \u002F>\n   \u003Csource media=\"(prefers-color-scheme: light)\" srcset=\"https:\u002F\u002Fapi.star-history.com\u002Fchart?repos=revfactory\u002Fharness&type=date&legend=top-left\" \u002F>\n   \u003Cimg alt=\"Star History Chart\" src=\"https:\u002F\u002Fapi.star-history.com\u002Fchart?repos=revfactory\u002Fharness&type=date&legend=top-left\" \u002F>\n \u003C\u002Fpicture>\n\u003C\u002Fa>\n\n\n## Key Features\n\n- **Agent Team Design** — 6 architectural patterns: Pipeline, Fan-out\u002FFan-in, Expert Pool, Producer-Reviewer, Supervisor, and Hierarchical Delegation\n- **Skill Generation** — Auto-generates skills with Progressive Disclosure for efficient context management\n- **Orchestration** — Inter-agent data passing, error handling, and team coordination protocols\n- **Validation** — Trigger verification, dry-run testing, and with-skill vs without-skill comparison tests\n\n\n## Workflow\n\n```\nPhase 1: Domain Analysis\n    ↓\nPhase 2: Team Architecture Design (Agent Teams vs Subagents)\n    ↓\nPhase 3: Agent Definition Generation (.claude\u002Fagents\u002F)\n    ↓\nPhase 4: Skill Generation (.claude\u002Fskills\u002F)\n    ↓\nPhase 5: Integration & Orchestration\n    ↓\nPhase 6: Validation & Testing\n```\n\n## Installation\n\n### Via Marketplace\n\n#### Add the marketplace\n```shell\n\u002Fplugin marketplace add revfactory\u002Fharness\n```\n\n#### Install the plugin\n```shell\n\u002Fplugin install harness@harness\n```\n\n### Direct Installation as Global Skill\n\n```shell\n# Copy the skills directory to ~\u002F.claude\u002Fskills\u002Fharness\u002F\ncp -r skills\u002Fharness ~\u002F.claude\u002Fskills\u002Fharness\n```\n\n## Plugin Structure\n\n```\nharness\u002F\n├── .claude-plugin\u002F\n│   └── plugin.json                 # Plugin manifest\n├── skills\u002F\n│   └── harness\u002F\n│       ├── SKILL.md                # Main skill definition (6-Phase workflow)\n│       └── references\u002F\n│           ├── agent-design-patterns.md   # 6 architectural patterns\n│           ├── orchestrator-template.md   # Team\u002Fsubagent orchestrator templates\n│           ├── team-examples.md           # 5 real-world team configurations\n│           ├── skill-writing-guide.md     # Skill authoring guide\n│           ├── skill-testing-guide.md     # Testing & evaluation methodology\n│           └── qa-agent-guide.md          # QA agent integration guide\n└── README.md\n```\n\n## Usage\n\nTrigger in Claude Code with prompts like:\n\n```\nBuild a harness for this project\nDesign an agent team for this domain\nSet up a harness\n```\n\n### Execution Modes\n\n| Mode | Description | Recommended For |\n|------|-------------|-----------------|\n| **Agent Teams** (default) | TeamCreate + SendMessage + TaskCreate | 2+ agents requiring collaboration |\n| **Subagents** | Direct Agent tool invocation | One-off tasks, no inter-agent communication needed |\n\n\u003Cp align=\"center\">\n  \u003Cimg src=\"harness_team.png\" alt=\"Harness Agent Team\" width=\"500\">\n\u003C\u002Fp>\n\n### Architecture Patterns\n\n| Pattern | Description |\n|---------|-------------|\n| Pipeline | Sequential dependent tasks |\n| Fan-out\u002FFan-in | Parallel independent tasks |\n| Expert Pool | Context-dependent selective invocation |\n| Producer-Reviewer | Generation followed by quality review |\n| Supervisor | Central agent with dynamic task distribution |\n| Hierarchical Delegation | Top-down recursive delegation |\n\n## Output\n\nFiles generated by Harness:\n\n```\nyour-project\u002F\n├── .claude\u002F\n│   ├── agents\u002F          # Agent definition files\n│   │   ├── analyst.md\n│   │   ├── builder.md\n│   │   └── qa.md\n│   └── skills\u002F          # Skill files\n│       ├── analyze\u002F\n│       │   └── SKILL.md\n│       └── build\u002F\n│           ├── SKILL.md\n│           └── references\u002F\n```\n\n## Use Cases — Try These Prompts\n\nCopy any prompt below into Claude Code after installing Harness:\n\n**Deep Research**\n```\nBuild a harness for deep research. I need an agent team that can investigate\nany topic from multiple angles — web search, academic sources, community\nsentiment — then cross-validate findings and produce a comprehensive report.\n```\n\n**Website Development**\n```\nBuild a harness for full-stack website development. The team should handle\ndesign, frontend (React\u002FNext.js), backend (API), and QA testing in a\ncoordinated pipeline from wireframe to deployment.\n```\n\n**Webtoon \u002F Comic Production**\n```\nBuild a harness for webtoon episode production. I need agents for story\nwriting, character design prompts, panel layout planning, and dialogue\nediting. They should review each other's work for style consistency.\n```\n\n**YouTube Content Planning**\n```\nBuild a harness for YouTube content creation. The team should research\ntrending topics, write scripts, optimize titles\u002Ftags for SEO, and plan\nthumbnail concepts — all coordinated by a supervisor agent.\n```\n\n**Code Review & Refactoring**\n```\nBuild a harness for comprehensive code review. I want parallel agents\nchecking architecture, security vulnerabilities, performance bottlenecks,\nand code style — then merging all findings into a single report.\n```\n\n**Technical Documentation**\n```\nBuild a harness that generates API documentation from this codebase.\nAgents should analyze endpoints, write descriptions, generate usage\nexamples, and review for completeness.\n```\n\n**Data Pipeline Design**\n```\nBuild a harness for designing data pipelines. I need agents for schema\ndesign, ETL logic, data validation rules, and monitoring setup that\ndelegate sub-tasks hierarchically.\n```\n\n**Marketing Campaign**\n```\nBuild a harness for marketing campaign creation. The team should research\nthe target market, write ad copy, design visual concepts, and set up\nA\u002FB test plans with iterative quality review.\n```\n\n## Coexistence — Harness and Neighbors\n\nHarness is not alone in the Claude Code \u002F agent-framework ecosystem. The following repos live in adjacent layers; each is described in a parallel \"X is …, Harness is …\" form so you can pick the one that fits your need or combine several.\n\n| Repo | Their position | Relationship to Harness |\n|------|----------------|-------------------------|\n| [coleam00\u002FArchon](https:\u002F\u002Fgithub.com\u002Fcoleam00\u002FArchon) | \"harness builder\" — deterministic, repeatable runtime configurations | **Same L3, neighbor sub-layer.** Archon is a Runtime-Configuration Factory, Harness is a Team-Architecture Factory. Pick Archon for runtime determinism, Harness for team architecture, or combine them. |\n| [SaehwanPark\u002Fmeta-harness](https:\u002F\u002Fgithub.com\u002FSaehwanPark\u002Fmeta-harness) | Codex port of the same concept | **Same L3, different runtime.** Use Harness on Claude Code, meta-harness on Codex. |\n| [affaan-m\u002FECC](https:\u002F\u002Fgithub.com\u002Faffaan-m\u002Feverything-claude-code) | \"Agent harness performance & workflow layer\" (sits on top of existing harnesses) | **Different layer.** ECC is a standardization layer across harnesses; Harness is a factory that generates harnesses. Serial combination possible. |\n| [wshobson\u002Fagents](https:\u002F\u002Fgithub.com\u002Fwshobson\u002Fagents) | Subagent \u002F skill catalog (182 agents, 149 skills) | **Factory ↔ parts supply.** wshobson is a catalog to shop from; Harness designs the team. Absorb wshobson entries as parts inside a Harness-generated team. |\n| [LangGraph](https:\u002F\u002Flangchain-ai.github.io\u002Flanggraph\u002F) | State-graph orchestration, LLM-agnostic | **Different track.** LangGraph is for long-running, state-recoverable orchestration; Harness is for fast Claude-Code-native team design. |\n\n## Built with Harness\n\n### Harness 100\n\n**[revfactory\u002Fharness-100](https:\u002F\u002Fgithub.com\u002Frevfactory\u002Fharness-100)** — 100 production-ready agent team harnesses across 10 domains, available in both English and Korean (200 packages total). Each harness ships with 4-5 specialist agents, an orchestrator skill, and domain-specific skills — all generated by this plugin. 1,808 markdown files covering content creation, software development, data\u002FAI, business strategy, education, legal, health, and more.\n\n### Research: A\u002FB Testing Harness Effectiveness\n\n**[revfactory\u002Fclaude-code-harness](https:\u002F\u002Fgithub.com\u002Frevfactory\u002Fclaude-code-harness)** — A controlled experiment across 15 software engineering tasks measuring the impact of structured pre-configuration on LLM code agent output quality.\n\n| Metric | Without Harness | With Harness | Improvement |\n|--------|:-:|:-:|:-:|\n| Average Quality Score | 49.5 | 79.3 | **+60%** |\n| Win Rate | — | — | **100%** (15\u002F15) |\n| Output Variance | — | — | **-32%** |\n\nKey finding: effectiveness scales with task complexity — the harder the task, the greater the improvement (+23.8 Basic, +29.6 Advanced, +36.2 Expert).\n\n**Exact phrasing to use everywhere:** +60% avg quality (49.5 → 79.3), 15\u002F15 win-rate, −32% variance (n=15, author-measured A\u002FB, third-party replications pending).\n\n> Full paper: *Hwang, M. (2026). Harness: Structured Pre-Configuration for Enhancing LLM Code Agent Output Quality.*\n\n## Requirements\n\n- [Agent Teams enabled](https:\u002F\u002Fcode.claude.com\u002Fdocs\u002Fen\u002Fagent-teams): `CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1`\n\n## FAQ\n\n\u003Cdetails>\n\u003Csummary>\u003Cb>Q1. Isn't \"+60%\" oversold?\u003C\u002Fb>\u003C\u002Fsummary>\n\n**A.** The +60% figure comes from an **author-measured A\u002FB (n=15, 15 tasks, measured on the sister repo `claude-code-harness`)**. Every citation in this repo pairs the number with the disclosure \"n=15, author-measured, third-party replications pending\" in the same sentence. For adoption decisions, we recommend running a 2–4 week internal pilot and measuring your own numbers.\n\n**Evidence:**\n- Author A\u002FB: [revfactory\u002Fclaude-code-harness](https:\u002F\u002Fgithub.com\u002Frevfactory\u002Fclaude-code-harness)\n- Paper: *Hwang, M. (2026). Harness: Structured Pre-Configuration for Enhancing LLM Code Agent Output Quality*\n\u003C\u002Fdetails>\n\n\u003Cdetails>\n\u003Csummary>\u003Cb>Q2. Why \"harness factory\" and not \"harness builder\"? Isn't this competing with Archon?\u003C\u002Fb>\u003C\u002Fsummary>\n\n**A.** Archon generates deterministic runtime configurations — it's a **Runtime-Configuration Factory**. Harness generates agent team architectures (team structure, message protocols, review gates) — it's a **Team-Architecture Factory**. They are **neighbor sub-layers of the same L3 Meta-Factory** and serve different needs. Pick Archon for runtime determinism, Harness for team-architecture patterns, or combine them (design architecture with Harness → deploy runtime with Archon).\n\n**Evidence:**\n- Archon self-definition: [clawfit docs\u002Freference-levels.md](https:\u002F\u002Fgithub.com\u002Fhongsw\u002Fclawfit\u002Fblob\u002Fmain\u002Fdocs\u002Freference-levels.md)\n- Sub-layer declaration: see the **Category — Where Harness Sits** section above\n- Archon repo: [github.com\u002Fcoleam00\u002FArchon](https:\u002F\u002Fgithub.com\u002Fcoleam00\u002FArchon)\n\u003C\u002Fdetails>\n\n\u003Cdetails>\n\u003Csummary>\u003Cb>Q3. Isn't \"Claude Code only\" too narrow? What about Gemini\u002FCodex?\u003C\u002Fb>\u003C\u002Fsummary>\n\n**A.** Currently the official runtime is Claude Code only. A Codex port of the same concept — [SaehwanPark\u002Fmeta-harness](https:\u002F\u002Fgithub.com\u002FSaehwanPark\u002Fmeta-harness) — is already public, so Codex teams can start there. Harness chose \"Claude-Code-native, deep\" over \"multi-runtime, shallow\"; cross-runtime collaboration with sibling repos (meta-harness, harness-init, OpenRig) is on the roadmap.\n\n**Evidence:**\n- Codex port: [github.com\u002FSaehwanPark\u002Fmeta-harness](https:\u002F\u002Fgithub.com\u002FSaehwanPark\u002Fmeta-harness)\n- Cross-runtime scaffolder: [github.com\u002FGizele1\u002Fharness-init](https:\u002F\u002Fgithub.com\u002FGizele1\u002Fharness-init)\n\u003C\u002Fdetails>\n\n## License\n\nApache 2.0\n","Harness 是一个用于 Claude Code 的团队架构工厂，能够根据领域描述自动生成由专业代理组成的团队及其所需技能。其核心功能包括通过六种预定义的团队架构模式来构建和配置代理团队，以及生成相关的技能文件。技术上，它利用了 Claude Code 的代理团队系统，将复杂的任务分解为协调一致的专业代理小组。此项目特别适合需要快速搭建和调整特定领域内多代理协作系统的场景，如开发自动化流程、数据处理流水线等。",2,"2026-06-11 03:52:07","high_star"]