What problem does it solve? Building a multi-agent automation setup from scratch requires deciding how to split work across agents, writing agent definitions, authoring skills, and wiring an orchestrator together. This Skill systematizes that entire process so a new domain or project gets a coherent, tested agent harness instead of ad-hoc prompts. ## Core Features & Use Cases - Harness Architecture Design: Audits existing agents/skills, analyzes the domain, and selects an execution mode (agent team, sub-agents, or hybrid) plus an architecture pattern such as pipeline, fan-out/fan-in, or supervisor. - Agent & Skill Generation: Creates agent definition files in .claude/agents/ and skill files in .claude/skills/ with pushy trigger descriptions, progressive disclosure, and team communication protocols. - Orchestration & Evolution: Builds an orchestrator skill with data-flow protocols, error handling, and test scenarios, registers a trigger pointer in CLAUDE.md, and maintains a change log so the harness keeps evolving with feedback. - Use Case: Ask to set up a harness for a content-pipeline project, and it audits the repo, defines researcher/writer/reviewer agents, generates their skills, builds an orchestrator, and validates triggers with should-trigger and near-miss queries. ## Quick Start Ask the agent to configure a harness for your project, for example by saying "이 프로젝트에 하네스 구성해줘" (set up a harness for this project).