Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →product-on-purpose/utility-pm-workflow-orchestrator
Run an ordered sequence of pm-skills against one input, pausing for go/no-go and stopping on a failed or empty step. Accepts a saved prioritized action plan (Mode A) or an ad-hoc named chain (Mode B; the chain command routes here). Explicit invocation only; run --dry-run first while the native path is EXPERIMENTAL. To author a durable workflow instead, use utility-pm-workflow-builder.
Passed 19 of 22 test cases with the skill, and 3 of 22 without it.
and 24 more in the full report
16 fixed3 passed either way3 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 16 test cases the skill fixed. Same model, same prompt, with and without the skill.
When running inside Claude Code with the native pm-skills plugin installed, which native tool does the orchestrator engine use to invoke downstream skills?
| Checked | Without skill | With skill |
|---|---|---|
| The response states that downstream skills are invoked using the Skill tool. | Passed | Passed |
| The response notes that invoked skills execute inline within the context window. | Missed | Passed |
The instructions your model reads when the skill loads.
Cross-client dispatch wrapper for the pm-workflow-orchestrator sub-agent. Detects the runtime; dispatches to the native sub-agent on Claude Code; reads agents/pm-workflow-orchestrator.md and walks the run loop inline on non-Claude clients via the "reference + execute inline" pattern. The orchestrator runs an ordered sequence of pm-skills from a saved prioritized-action-plan (Mode A) or a user-named chain (Mode B), pausing for go/no-go by default and stopping on a failed or empty step.
Status summary (updated v2.26.0): smoke-tested on the native Claude Code path; EXPERIMENTAL elsewhere.
- Claude Code (native): Mode B chains SMOKE-TESTED PASS (2026-06-10, installed plugin). The live run confirmed the engine invokes downstream skills via the
Skilltool and that they execute INLINE in the engine's context (the Skill tool injects the target SKILL.md into the caller's context; no sub-agent is spawned), with real artifacts produced and the checkpoint pause honored. Mode A native runs and a single continuous interactive engine instance across multiple checkpoints have not yet been exercised; details and caveats in the compatibility matrix's v2.26.0 smoke-gate record.- All non-Claude clients (Codex CLI, Cursor, Windsurf, Copilot CLI, Gemini CLI): EXPERIMENTAL until a dedicated maintainer-gate test exercises a real multi-artifact inline WRITE run. The orchestrator writes up to three full PM artifacts and may thread state; this is strictly harder than the conductor's inline path and has never been live-validated off Claude Code.
On ANY client, run
--dry-runFIRST as the readiness check (it exercises parsing, checkpointing, stop-on-fail, and the tool-capability pre-flight without invoking consequential skills). See the Sub-Agent Compatibility Matrix for the canonical safe-usage matrix.
foundation-prioritized-action-plan and want to run its runnable Section 7 prompts in order, pausing for go/no-go (Mode A).deliver-prd then deliver-user-stories. On Claude Code, the /chain command is the terse front door for this mode.workflow-* command.Run modes (orthogonal to client):
--auto, opt-in): run without pausing on clean steps; still stop on failed, pause on empty, and stay checkpointed for Complex / Chaotic plans unless --force-auto.--thread declares a linear dependency so each step receives the prior step's confirmed artifact; see the Mode B Chain Expression Contract in references/PARSE-CONTRACT.md.
workflow-* command (workflow-foundation-sprint, workflow-customer-discovery, ...). The orchestrator does NOT supersede those and surfaces a workflow step as MANUAL rather than nesting it.foundation-prioritized-action-plan (which can then offer to hand its plan here).utility-pm-critic.utility-pm-workflow-builder. That skill produces a durable, named workflow; this one runs an ephemeral chain and persists no definition.Runtime detection step. Determine which AI client is invoking this skill. Run mode (checkpointed vs auto) comes from the user's flags and is independent of the client.
Invoke @agent-pm-skills:pm-workflow-orchestrator with the user's input plus any flags from $ARGUMENTS (--auto, --force-auto, --dry-run). The native sub-agent parses the input, builds the step list, and delegates each step via the Skill tool to the real downstream skill, running its own per-step loop with confirmation pauses. Relay the engine's per-step output blocks and the terminal output to the user.
test cases passed, vs 3 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.