dispatch-as-project-agentlisted

# Dispatch As Project Agent ## Purpose In Claude Code, project-level agents at `<project>/.claude/agents/<role>.md` are NOT natively discoverable as `subagent_type` values by the Agent tool. The Agent tool only resolves the runtime built-ins (`general-purpose`, `Explore`, `Plan`, `claude-code-guide`, `statusline-setup`). This is a Claude Code limitation, not a YakOS one (incident:v0.2.0). **v0.3.0+: yakos start solves this for whole sessions.** Launching via `yakos start <project>` composes a `--agents` JSON object from both framework + project agent files and passes it on the claude command line — project agents become addressable as `subagent_type` for the session's lifetime. If you started the session with `yakos start`, you do NOT need this skill for the common case. **v0.4.2+: yakos dispatch covers cross-runtime + non-yakos-start sessions.** When the lead needs to dispatch a project agent in a session that wasn't launched via `yakos start` (e.g. a bare `claude` session), or wants to route the specialist to a different runtime (codex / gemini) than the lead, run from a Bash tool: yakos dispatch <agent-name> "<task description>" This shells out to the right runtime CLI per the agent's frontmatter `runtime:` field, runs the agent non-interactively, and returns the captured output. Audit trail at `~/.yakos-state/dispatch-log.ndjson`. **This skill (the inline-injection technique) is still useful** for two cases: 1. Read-only diagnosis tasks that should run inside t