harness/.claude-plugin/marketplace.json
ythong 01d82a46f6 fix: correct Agent Teams API usage in harness/zio-harness skills
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>
2026-06-17 17:27:39 +09:00

23 lines
848 B
JSON

{
"name": "ythong-harness",
"owner": {
"name": "ythong",
"email": "ythong86@gmail.com",
"url": "https://git.zioinfo.co.kr/ythong"
},
"plugins": [
{
"name": "harness",
"source": "./",
"description": "에이전트 팀 & 스킬 아키텍트. 도메인/프로젝트에 맞는 하네스를 구성하고, 전문 에이전트를 정의하며, 에이전트가 사용할 스킬을 생성하는 메타 스킬.",
"version": "1.3.1"
},
{
"name": "zio-harness",
"source": "./plugins/zio-harness",
"description": "React + Spring Boot + Mobile App 풀스택 개발 하네스. orchestrator·analyst·bot·agent 에이전트 팀이 기능 개발·테스트·배포를 파이프라인으로 처리. PROJECT_MAP.md로 폴더 구조를 세션 간 기억.",
"version": "1.0.1"
}
]
}