orchestrate

To route workflow artifacts across plugins, you need a coordination mechanism that detects the current phase and passes artifacts to the appropriate next skill while enforcing boundaries. This preserves artifact continuity without performing the actual work.

Cross-plugin workflow orchestration is the process of coordinating phase transitions like brainstorm, plan, work, review, and compound across different plugins. It ensures explicit routing decisions and artifact presence checks without executing the work itself.

Moving a task through phases requires a routing skill to detect the current workflow phase and explicitly negotiate the next step. It provides non-destructive guidance and uses user prompts to confirm transitions and preserve artifacts.

Yes, enforcing boundaries during phase transitions is possible by using non-destructive guidance and explicit user negotiation. The workflow routing mechanism requires artifact presence checks and uses dialogs to confirm next steps before proceeding.

No, workflow routing does not perform the work. It coordinates and routes artifacts across plugins to ensure correct phase transitions, acting only as a routing mechanism with safeguards rather than executing the phase work itself.

The main limitation is that a routing skill cannot perform the actual work of the phase it routes to. It requires explicit routing decisions and artifact presence checks, relying on user negotiation through dialogs to proceed safely.