The skills (and the harness orchestrator templates) invoked TeamCreate with an inline members[] array and TaskCreate with a tasks[] array plus assignee/depends_on — none of which match the real experimental Agent Teams API. Rewrite to the documented flow: - TeamCreate creates an empty team (team_name only) - teammates are spawned via the Agent tool (team_name + name + subagent_type) - tasks are created one-per-call (subject/description); ownership via TaskUpdate.owner, dependencies via TaskUpdate.blockedBy - zio-harness now uses custom agent/bot subagent types instead of general-purpose, and the orchestrator is the team lead (not a spawned member) - add shutdown_request + TeamDelete cleanup and note the CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1 requirement Bump harness 1.3.0 -> 1.3.1, zio-harness 1.0.0 -> 1.0.1. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
32 lines
1.1 KiB
JSON
32 lines
1.1 KiB
JSON
{
|
|
"name": "harness",
|
|
"description": "The team-architecture factory for Claude Code — a meta-skill that turns a domain description into an agent team and the skills they use, with six pre-defined team-architecture patterns (Pipeline, Fan-out/Fan-in, Expert Pool, Producer-Reviewer, Supervisor, Hierarchical Delegation). Claude Code용 팀 아키텍처 팩토리: 도메인 한 문장을 에이전트 팀과 스킬 세트로 변환하는 메타 스킬.",
|
|
"version": "1.3.1",
|
|
"author": {
|
|
"name": "ythong",
|
|
"url": "https://git.zioinfo.co.kr/ythong"
|
|
},
|
|
"homepage": "https://git.zioinfo.co.kr/ythong/harness",
|
|
"repository": "https://git.zioinfo.co.kr/ythong/harness",
|
|
"license": "Apache-2.0",
|
|
"keywords": [
|
|
"harness",
|
|
"harness-factory",
|
|
"team-architecture-factory",
|
|
"agent-team",
|
|
"skill-architect",
|
|
"meta-skill",
|
|
"orchestration",
|
|
"claude-code",
|
|
"claude-code-plugin",
|
|
"agent-scaffolding",
|
|
"multi-agent",
|
|
"pipeline",
|
|
"fan-out-fan-in",
|
|
"expert-pool",
|
|
"producer-reviewer",
|
|
"supervisor",
|
|
"hierarchical-delegation"
|
|
]
|
|
}
|