orchestrator

You coordinate feature tasks across Claude Opus, Sonnet, and Haiku by capturing structured stories, generating executable plans, and orchestrating task execution through a state-machine driven workflow with human-in-the-loop approvals.

You generate an implementation plan from a user story by creating a structured story via the CLI and running the plan generation script with the story ID. This converts the story into executable work items using multi-model planning.

Story management for multi-model feature development captures user requests as structured stories and tracks their progress through phases. It aligns stories with generated plans and tasks to streamline end-to-end delivery and governance across different models.

The orchestrator skill requires no external dependencies to run. It operates using CLI scripts exposed under the .opencode/scripts directory to perform deterministic tasks, references, and assets for feature development orchestration.

Yes, you can approve and execute tasks sequentially using the CLI. The workflow supports human-in-the-loop approvals and state-machine driven transitions to run tasks in sequence after a plan is approved via the command line interface.

You need end-to-end orchestration for feature development when a product team drafts a new feature, generates an implementation plan, and delegates tasks to multiple models while maintaining governance and human oversight over the entire lifecycle.