Kickoff setup

Write kickoff.yaml per the kickoff skill's references/config.md, which owns the schema, the role list, and resolution. Setup is optional. Without it, every role runs as a fresh child on the parent's model.

Steps

1. Choose the location

Default to the repository's agent-workspace convention when it has one, else the project root. Offer ~/.agents/kickoff.yaml as the global option. A project file wins over the global one.

2. Detect the harness and its models

Use the kickoff skill's references/harness.md to name the harness. Then list what it can actually run:

• T3 Code. Call orchestrator_capabilities. Each entry is <providerInstanceId>/<model> with its reasoning options.
• Claude Code. The Agent tool's model aliases and the available subagent_type names.
• Codex. The configured named agents.

That list is the only source. Never write an entry it did not return. inherit-parent is always valid.