ir:onboarding-factory/create-agent

create-agent

You run as a focused subagent with no parent context. Do the research yourself (web + file access). This task runs NO recording and invokes NO agent CLI. When done, return only the "Return contract" block.

What this does

Adds a new agent COLUMN to the matrix — the counterpart to create-scenario's ROW. It does three things, all up front, before any cell is assessed or recorded:

1. Register the column via of agent add — writes replaydata/agents/<slug>/metadata.json {id, name, provider, prerequisites[]} and registers the agent in the catalog meta.min_versions so of status and the viewer treat it as onboarded.
2. Scaffold the interactive driver from the template so record has something to drive.
3. Predict driver-needs — across the scenario catalog, name the step types the agent's recipes will need, so the driver gaps are known before the assess sweep instead of being rediscovered one record round-trip at a time.

Prerequisite: the Go adapter (maintainer / code task)

The daemon only observes an agent it has an adapter for. Wiring a new adapter is a Go change (a package under core/adapters/inbound/agents/<slug>/ exporting Agent(), plus one line in the All() slice in core/adapters/inbound/agents/all.go). That is out of scope for this skill. If no adapter exists yet, say so in notes: the column can be registered and the driver scaffolded, but recordings can't be observed until the adapter lands. Don't block — register what you can.

Steps

1. Research the agent

Use web search + fetch on the agent's official site, changelog, and source repo. Determine:

• id — kebab slug (the column key, the replaydata/agents/<id>/ dir).
• name — display name (e.g. "Claude Code").
• provider — anthropic / openai / google / … (the model vendor).
• prerequisites — the human actions a recording needs that the subagent can't perform: auth mode (subscription vs API key), env vars, a local model server, a config file. These become --prereq strings and are surfaced by of record prereq-check before every recording. Be concrete — "switch the CLI from subscription auth to an API key (ANTHROPIC_API_KEY)" beats "set up auth".
• transport shape — does it write an append-only transcript under $HOME (FilesUnderRoot), one transcript per cwd (FilesUnderCWD), or a structured store / SQLite (ProcessOwnedStore)? This determines what the daemon can see and feeds the driver scaffold + later assessments. Read sibling adapters under core/adapters/inbound/agents/ for the three variants.