workflow-orchestrator

Multi-skill workflow orchestration is automated by defining milestone hooks in your SKILL.md files, which trigger follow-up actions across multiple skills automatically. This coordinates cross-skill workflows like PRD creation and implementation handoffs without manual intervention.

Hook definitions in SKILL.md files specify triggers like after_complete and on_error to determine which skills run next and in what mode. They enable milestone-driven automation by chaining skills together based on execution outcomes.

Yes, you can control execution modes using mode-based triggers defined in your hooks. Supported modes include auto, background, and ask_first, allowing you to dictate whether follow-up actions run immediately, silently, or require user confirmation.

You can track progress and context during cross-skill workflow coordination through built-in observability features. The orchestrator logs progress and contextual data to session-logger, ensuring full traceability across the entire workflow lifecycle.

No additional dependencies are required to automate milestone-driven workflows. You only need to define the appropriate hook definitions in your existing skills' SKILL.md files to enable automated workflow chaining and milestone-based handoffs.

The best way to handle errors during automated multi-skill execution is by defining on_error hooks in your SKILL.md. These hooks allow the orchestrator to trigger specific follow-up actions or recovery skills when a milestone fails.