workflow-planner

Convert confirmed user intent into validated workflow plans with owners, approvals, and recovery routes.

Updated Aug 1, 2026
One-click install
npx skills add https://github.com/QuyDu/Skills-Orchestrator --skill workflow-planner-quydu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: workflow-planner
Source: https://github.com/QuyDu/Skills-Orchestrator/tree/main/.github/skills/workflow-planner
Command: npx skills add https://github.com/QuyDu/Skills-Orchestrator --skill workflow-planner-quydu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a confirmed request into a safe, executable sequence of steps is error-prone: steps can lack owners, contain dependency cycles, skip approval gates, or have no recovery path when something fails. This Skill converts clarified user intent into an ordered, schema-validated workflow plan with explicit ownership, checkpoints, rollback points, and terminal handoff routes. ## Core Features & Use Cases - Structured Plan Generation: Emits machine-readable (JSON, schema 1.1) and Markdown workflow plans with identical ordering, unique step IDs, and exactly one ready prerequisite-free starting step. - Ownership and Dependency Validation: Assigns every step one skill owner or explicit operator owner, rejects cyclic plans, and validates against the skill catalog and dependency graph. - Risk Controls and Recovery: Inserts approval gates for destructive or external mutations and defines onBlocked/onFailed recovery branches that all reach a terminal project-handoff step. - Use Case: After clarifying a request to remediate security audit findings, produce a gated plan that sequences review, planning, and approved execution phases, with rollback points and a handoff route if any step fails. ## Quick Start Ask the agent to use the workflow-planner skill to turn the confirmed clarification result into an ordered workflow plan with owners, approval gates, and recovery routes.

Frequently Asked Questions about workflow-planner

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I turn a confirmed request into an executable workflow plan?

Run the workflow-planner skill after clarification completes. It resolves the confirmed objective into candidate steps owned by available skills, orders them by dependency evidence, and emits schema 1.1 JSON and Markdown plans with identical ordering.

How does workflow planning handle approval for destructive actions?

The planner inserts explicit approval gates tied to concrete destructive, privileged, external, or irreversible mutation steps. Operator-owned steps act as approval gates and are never inferred as executable skills.

What happens when a workflow step fails or gets blocked?

Every nonterminal step must define onBlocked and onFailed recovery branches, and both routes must reach a terminal project-handoff step. The handoff records partial outcomes and one next action.

Can the planner execute the workflow plan it creates?

No. The skill only produces and validates the plan; it does not execute it. Execution is handled downstream, and the planner appends a workflow-planned event plus synchronized execution state for tracking.

Why does workflow planning fail with a blocked output?

Planning fails closed when ownership mapping or dependency evidence is incomplete, or when clarification is blocked by material ambiguity. It returns a blocked plan listing unresolved prerequisites rather than publishing a plan with ambiguous step authority.