Commit Graph

2 Commits

Author SHA1 Message Date
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
ythong
cc46c4528e feat: split zio-harness into a standalone plugin
Move skills/zio-harness into plugins/zio-harness/ as a self-contained
plugin with its own .claude-plugin/plugin.json. Add a second marketplace
entry (zio-harness@1.0.0) and bump the harness plugin to 1.3.0 since it no
longer bundles zio-harness. Single ownership: harness ships only the
harness skill, zio-harness ships only the zio-harness skill.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-17 16:54:17 +09:00