harness-subagentlisted

# /harness-subagent Use this skill to create and manage `subagent` entities in the agent-harness workspace. A subagent is a specialized agent definition — with a name, description, optional tool restrictions, and an optional model override — that harness renders into provider-native agent configuration files for every enabled provider. --- ## What is a subagent entity? A subagent entity is a single canonical Markdown source file under `.harness/src/subagents/<subagent-id>.md`. It contains: - **Required YAML frontmatter**: `name` and `description` - **Optional frontmatter**: provider-specific fields set via override sidecars (model, tools, handoffs) - **Body**: Markdown prose that becomes the agent's system prompt Harness renders one output artifact per enabled provider from that single source file. You edit the source once; all provider files stay in sync. --- ## Provider output mapping ### Claude Code | Item | Value | |------|-------| | Output path | `.claude/agents/<subagent-id>.md` | | Format | Markdown with YAML frontmatter | | Required frontmatter | `name`, `description` | | Optional frontmatter | `tools` (string or `string[]`), `model` | Claude Code loads agent files from `.claude/agents/` at session start. Each file's `description` field tells Claude when to delegate to that agent. Claude routes tasks automatically, or the user can invoke an agent explicitly with `@agent-<name>` or the `/agents` command. Supported `model` values: `sonnet`, `opus`, `haiku`, a