team-to-orchestra

Converting PROJECT.md and kickoff.yaml into an orchestra.yaml file involves mapping project names, phase goals, system contexts, and teammate dependencies into the structured schema required by the agent-orchestra CLI.

Mapping inter-phase dependencies to team dependencies in orchestra.yaml requires parsing your kickoff configuration and translating phase relationships into the team dependency structure recognized by the agent-orchestra CLI.

Generating tasks with deliverables and verification commands from teammate focus areas is possible by converting team configuration files into an orchestra.yaml schema that structures focus areas into actionable, verifiable tasks.

You do not need to manually write the orchestra.yaml schema to run multi-phase projects with the agent-orchestra CLI; you can automate the conversion of human-readable project and team configuration files into the machine-readable format.

Generating an orchestra.yaml file for project scaffolding is necessary after defining a multi-phase project using initialization skills, producing the configuration file required to execute the project with the agent-orchestra CLI.