orchestrate

You can coordinate multi-modality work by classifying user intent, decomposing it into sub-tasks, and routing each to the appropriate modality while gating progress on published artifacts tracked via GitHub issues.

Artifact-driven task routing is a process that decomposes a multi-step intent into sub-tasks, classifies each by modality, and enforces explicit dependencies and state labels to gate progression across different workflow phases.

You decompose a multi-step goal by classifying the initial intent and routing each resulting sub-task to a designated modality, such as spec, architect, implement, or verify, to handle its specific lifecycle state transitions.

Yes, this orchestration approach works with GitHub issues by automatically tracking and publishing parent epic progress, creating sub-tasks, and managing cross-skill invocations for an auditable end-to-end workflow.

You need artifact-based governance for end-to-end orchestration when your goals require coordination across multiple modalities with explicit dependencies and lifecycle state transitions tracked on GitHub.

The best way to structure a workflow plan is to draft a structured orchestration plan for the multi-modality goal and dispatch the first sub-task to its designated modality to initiate the gated progression.