New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Utility Pm Workflow Orchestrator

by product-on-purpose in product-on-purpose/pm-skills

Run an ordered sequence of pm-skills against one input, pausing for go/no-go and stopping on a failed or empty step.

Apache-2.0Auto-check passedAgent Workflows

Install Utility Pm Workflow Orchestrator

skills CLI
$ npx skills add product-on-purpose/pm-skills --skill utility-pm-workflow-orchestrator -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install product-on-purpose/pm-skills utility-pm-workflow-orchestrator --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/product-on-purpose/pm-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/utility-pm-workflow-orchestrator .claude/skills/utility-pm-workflow-orchestrator && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
utility-pm-workflow-orchestrator
GitHub stars
716
Token cost
~2.5k tokens
SKILL.md length
1,237 words
Files
6 (incl. references)
Skills in repo
68
Repo updated
First seen
Licence
Apache-2.0

At a glance

Run an ordered sequence of pm-skills against one input, pausing for go/no-go and stopping on a failed or empty step.

  • Works in 7 steps: Tool-capability pre-flight (FIRST… → Read the canonical sub-agent definition… → Read the shared parse and step-status… → …
  • Tasks that involve Planning
  • SKILL.md covers When to Use, When NOT to Use, Instructions and --dry-run (readiness probe;…, plus 2 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Utility Pm Workflow Orchestrator is an agent skill from product-on-purpose/pm-skills. 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.

Its SKILL.md is about 2.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 7 other files, including reference files (for example `HISTORY.md`, `evals/trigger-fixtures.json` and `references/EXAMPLE.md`).

It sits in Agent Workflows, covering Planning and Feature launches and release readiness. The repository describes itself as: 68 plug-and-play, best-practice product management skills for AI agents: 30 Triple Diamond phase + 11 foundation + 12 utility + 15 tool (Foundation Sprint + Design Sprint). Plus… The licence is Apache-2.0.

When your agent uses it

  • Tasks that involve Planning
  • Tasks that involve Feature launches and release readiness

Example prompts

  • “/utility-pm-workflow-orchestrator”

Workflow steps

7 steps, taken from the first numbered list in SKILL.md.

  1. Tool-capability pre-flight (FIRST action, before parsing or step 1). Verify the client can (a) write a file under…
  2. Read the canonical sub-agent definition at agents/pm-workflow-orchestrator.md.
  3. Read the shared parse and step-status contract at references/PARSE-CONTRACT.md (the engine reads the same file; this is what keeps the…
  4. Execute the engine body as your operating instructions: run the pre-flight refusals, build the ordered step list (Mode A parse or Mode B…
  5. At each step, read the downstream skill's SKILL.md and execute its method inline in this window; classify the return PRODUCED / EMPTY /…
  6. Honor the run mode: pause at each OK step in CHECKPOINTED; auto-advance only unambiguously-PRODUCED steps in GUARDED AUTO; a FAILED step…
  7. Emit the terminal output (run complete or halted) per the engine's section 4.5.

What it can do on your machine

Read from SKILL.md and the folder at commit 1cef1a9. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Utility Pm Workflow Orchestrator loads about 2.5k tokens when it runs, and up to ~7.5k if it reads all its reference files. Until then it costs about 105 tokens; SKILL.md has 1,237 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~105
When it runs · the whole SKILL.md, loaded when a task matches
~2.5k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~7.5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from product-on-purpose/pm-skills at commit 1cef1a9, republished under its Apache-2.0 licence (© product-on-purpose). 1,237 words, ~2,471 tokens.

Download SKILL.mdSave it as .claude/skills/utility-pm-workflow-orchestrator/SKILL.md (or your agent's skills folder). This skill also uses 5 other files; get the full folder from GitHub.
name
utility-pm-workflow-orchestrator
description
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.
license
Apache-2.0
metadata.classification
utility
metadata.version
1.2.0
metadata.updated
2026-06-10
metadata.category
workflow
metadata.frameworks
triple-diamond
metadata.author
product-on-purpose
<!-- PM-Skills | https://github.com/product-on-purpose/pm-skills | Apache 2.0 -->

PM Workflow Orchestrator (Dispatch Skill)

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 Skill tool 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-run FIRST 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.

When to Use

  • You produced a foundation-prioritized-action-plan and want to run its runnable Section 7 prompts in order, pausing for go/no-go (Mode A).
  • You want to run an ad-hoc, user-named chain of pm-skills against shared context (Mode B), for example deliver-prd then deliver-user-stories. On Claude Code, the /chain command is the terse front door for this mode.
  • You want a generic runner for a dynamic chain that is NOT a pre-curated workflow-* command.

Run modes (orthogonal to client):

  • CHECKPOINTED (default): pause after each OK step for approve / edit / skip / redo.
  • GUARDED AUTO (--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.

When NOT to Use

  • You want a fixed, curated, named chain that an author maintains by hand (for example a full Foundation Sprint or Customer Discovery) -> use the existing 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.
  • You only need to PRODUCE a prioritized action plan (not run it) -> use foundation-prioritized-action-plan (which can then offer to hand its plan here).
  • You only need to review one artifact -> use utility-pm-critic.
  • You want to run library-maintenance machinery as if it were PM work -> the orchestrator refuses Tier-3 maintenance skills.
  • You want to AUTHOR a reusable workflow rather than run a chain right now -> use utility-pm-workflow-builder. That skill produces a durable, named workflow; this one runs an ephemeral chain and persists no definition.

Instructions

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.

If you are running in Claude Code with the pm-skills plugin installed

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.

This path is EXPERIMENTAL at v2.24.0 (see Status summary). Instruct the user to run --dry-run first.

Show full SKILL.md (592 more words)Show less
If you are running in any other AI client

Codex CLI, Cursor, Windsurf, Copilot CLI, Gemini CLI, or any client without native pm-skills plugin sub-agent support:

  1. Tool-capability pre-flight (FIRST action, before parsing or step 1). Verify the client can (a) write a file under _pm-skills/plan-orchestrator/<run>/ and (b) run any Bash a downstream skill needs.
    • If file write is unavailable: degrade explicitly to CHAT-ONLY mode (warn that multi-step reliability drops and context budget rises because full artifacts must stay in-window) for short runs, or refuse a long run with a clear message. Do not fail mid-chain.
    • If Bash is unavailable for a step that needs it: surface that step as blocked at its boundary.
    • Record the detected capabilities; they govern disk-write below.
  2. Read the canonical sub-agent definition at agents/pm-workflow-orchestrator.md.
  3. Read the shared parse and step-status contract at references/PARSE-CONTRACT.md (the engine reads the same file; this is what keeps the inline branch and the engine from drifting).
  4. Execute the engine body as your operating instructions: run the pre-flight refusals, build the ordered step list (Mode A parse or Mode B named chain), then walk the per-step loop.
  5. At each step, read the downstream skill's SKILL.md and execute its method inline in this window; classify the return PRODUCED / EMPTY / FAILED with the rubric in references/PARSE-CONTRACT.md; write NN-<skill-name>.md to the run directory when disk-write is on.
  6. Honor the run mode: pause at each OK step in CHECKPOINTED; auto-advance only unambiguously-PRODUCED steps in GUARDED AUTO; a FAILED step STOPS the run; an EMPTY or ambiguous step always pauses for confirmation (a forced checkpoint pause the user can clear), regardless of --force-auto.
  7. Emit the terminal output (run complete or halted) per the engine's section 4.5.

The "reference + execute inline" pattern is what enables cross-client compatibility. It is EXPERIMENTAL here until the maintainer-gate WRITE harness validates a real multi-artifact run on each client.

--dry-run (readiness probe; run this FIRST on any client)

--dry-run walks the full step list and exercises parsing, checkpointing, stop-on-fail, and the tool-capability pre-flight, but does NOT invoke any consequential downstream skill. Each step emits "NOT EXECUTED - dry run" plus what WOULD happen (which skill, which mode, whether disk-write would engage). Use it to confirm the plan parses, the chain resolves, and the client has the tool access the live run needs, before spending tokens on real delegation.

Cross-Client Notes

Because non-Claude clients run the loop and every step inline in ONE context window:

  1. Context budget. The combined budget (engine body + per-step downstream skill reads + produced artifacts) can approach context limits on multi-step runs. The engine auto-enables disk-write for 2+ step runs and keeps only a one-line summary per completed step in context; CHAT-ONLY mode loses that mitigation, so prefer a write-capable client for long chains.
  2. Tool authorization. Inline execution must have file-write and Bash access (not Read-only). The pre-flight (step 1 above) checks this. Codex may need its sandbox write flag enabled; Cursor and Gemini may interpose approval gates per step.
  3. No native chaining. This is why the engine delegates by Skill (Claude Code) or inline read-and-execute (non-Claude), never by spawning a sub-agent. A Mode A step that resolves to a dispatch skill which would fan out to a sub-agent (only utility-pm-critic) is handled by inlining the leaf agent, never by chaining (engine section 7.2).

Reference Files

© product-on-purpose, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 5 other files (references) in skills/utility-pm-workflow-orchestrator of product-on-purpose/pm-skills.

  • SKILL.md
  • HISTORY.md
  • evals/trigger-fixtures.json
  • references/EXAMPLE.md
  • references/PARSE-CONTRACT.md
  • references/TEMPLATE.md

Open the folder on GitHubat commit 1cef1a9

Compare with similar skills

Utility Pm Workflow Orchestrator next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Utility Pm Workflow Orchestrator compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Utility Pm Workflow Orchestrator this skillproduct-on-purpose/pm-skills716—~2.5kAutomated safety check: PassApache-2.0
Agent Workflowmenkesu/awesome-pm-skills434—~5.2kAutomated safety check: PassCustom licence
Prod Activation Planevolution-foundation/evo-nexus545—~2.9kAutomated safety check: PassCustom licence
Rfc Writermohitagw15856/pm-claude-skills1.4k—~4.1kAutomated safety check: PassMIT
SpikeDeL-TaiseiOzaki/claude-code-orchestra199—~6.9kAutomated safety check: PassMIT
Todos Reviewhanamizuki/solopreneur152—~2.2kAutomated safety check: PassMIT

Similar skills

  • Agent Workflow

    menkesu/awesome-pm-skills

    Sets up how you and your team build and work with AI agents, and produces an Agent Workflow Charter (agent lanes, plan-mode loop, autonomy ladder with promotion criteria, rules file, review policy…

    434 GitHub stars~5.2k tokensUpdated 4 days ago
    Agent WorkflowsAuto-check passed

  • Prod Activation Plan

    evolution-foundation/evo-nexus

    Create a phased activation plan using the EvoNexus standard structure — single index file + folder-per-phase + file-per-item, each item detailed with owner, dependencies, decisions pending…

    545 GitHub stars~2.9k tokensUpdated 5 mo ago
    Agent WorkflowsAuto-check passed

  • Rfc Writer

    mohitagw15856/pm-claude-skills

    Write an engineering RFC (Request for Comments) for a technical decision, architectural change, or significant implementation approach.

    1.4k GitHub stars~4.1k tokensUpdated yesterday
    Agent WorkflowsAuto-check passed

  • Spike

    DeL-TaiseiOzaki/claude-code-orchestra

    Time-boxed technical investigation/feasibility study with Codex-first multi-agent collaboration (Codex + Opus 4.6 + Agent Teams).

    199 GitHub stars~6.9k tokensUpdated 20 days ago
    Agent WorkflowsAuto-check passed

  • Todos Review

    hanamizuki/solopreneur

    Deep-review a single todo or backlog item to decide whether it is worth building: problem clarity, solution quality, and implementation priority.

    152 GitHub stars~2.2k tokensUpdated 14 days ago
    Agent WorkflowsAuto-check passed

  • Refactor Design Report

    penwyp/ClaudePreference

    Produce a professional, code-grounded refactor or implementation design report from identified technical problems, product gaps, review findings, architecture concerns, or frontend-backend contract…

    136 GitHub stars~1.4k tokensUpdated 4 mo ago
    Product & Project ManagementAuto-check passed

More from product-on-purpose/pm-skills

All 68 skills in this repo

  • Define Hypothesis

    product-on-purpose/pm-skills

    Defines a testable hypothesis with clear success metrics and a validation approach.

    716 GitHub stars~966 tokensUpdated 2 days ago
    Auto-check passed

  • Define Jtbd Canvas

    product-on-purpose/pm-skills

    Creates a Jobs to be Done canvas capturing the functional, emotional, and social dimensions of a customer job.

    716 GitHub stars~1.1k tokensUpdated 2 days ago
    Auto-check passed

  • Define Opportunity Tree

    product-on-purpose/pm-skills

    Creates an opportunity solution tree connecting a desired outcome to customer opportunities and candidate solutions, preventing solution-first jumps in continuous discovery.

    716 GitHub stars~1.1k tokensUpdated 2 days ago
    Auto-check passed

  • Define Problem Statement

    product-on-purpose/pm-skills

    Creates a clear problem framing document with user impact, business context, and success criteria.

    716 GitHub stars~932 tokensUpdated 2 days ago
    Auto-check passed

  • Deliver Acceptance Criteria

    product-on-purpose/pm-skills

    Generates structured Given/When/Then acceptance criteria for a user story or feature slice, covering the happy path, key failure scenarios, and non-functional expectations in testable form.

    716 GitHub stars~1k tokensUpdated 2 days ago
    Auto-check passed

  • Deliver Launch Checklist

    product-on-purpose/pm-skills

    Creates a cross-functional pre-launch checklist covering engineering, design, marketing, support, legal, and operations readiness, with owners, dates, and go/no-go criteria so nothing is missed…

    716 GitHub stars~970 tokensUpdated 2 days ago
    Auto-check passed

Categories

Questions about Utility Pm Workflow Orchestrator

What does Utility Pm Workflow Orchestrator do?

Run an ordered sequence of pm-skills against one input, pausing for go/no-go and stopping on a failed or empty step. Utility Pm Workflow Orchestrator is an agent skill from product-on-purpose/pm-skills. Run an ordered sequence of pm-skills against one input, pausing for go/no-go and stopping on a failed or empty step.

When should I use Utility Pm Workflow Orchestrator?

Utility Pm Workflow Orchestrator fits situations like: tasks that involve Planning; tasks that involve Feature launches and release readiness.

How do I install Utility Pm Workflow Orchestrator in Claude Code?

Run `npx skills add product-on-purpose/pm-skills --skill utility-pm-workflow-orchestrator -a claude-code`. Or copy the skill folder (skills/utility-pm-workflow-orchestrator in product-on-purpose/pm-skills) into .claude/skills/utility-pm-workflow-orchestrator in your project. Claude Code loads it when a task matches its description.

How do I install Utility Pm Workflow Orchestrator in Codex?

Run `npx skills add product-on-purpose/pm-skills --skill utility-pm-workflow-orchestrator -a codex`. Or copy the skill folder (skills/utility-pm-workflow-orchestrator in product-on-purpose/pm-skills) into .agents/skills/utility-pm-workflow-orchestrator in your project. Codex loads it when a task matches its description.

Can I use Utility Pm Workflow Orchestrator in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add product-on-purpose/pm-skills --skill utility-pm-workflow-orchestrator -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/utility-pm-workflow-orchestrator, .gemini/skills/utility-pm-workflow-orchestrator, .github/skills/utility-pm-workflow-orchestrator and .opencode/skills/utility-pm-workflow-orchestrator in your project.

What does Utility Pm Workflow Orchestrator need to run?

SKILL.md names no scripts, command-line tools or credentials: Utility Pm Workflow Orchestrator is instructions for the agent only.

Does Utility Pm Workflow Orchestrator access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Utility Pm Workflow Orchestrator safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Utility Pm Workflow Orchestrator use?

Utility Pm Workflow Orchestrator is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Utility Pm Workflow Orchestrator use?

About 2.5k tokens (SKILL.md is roughly 9.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 5k tokens, read only when the agent opens those files.

What are the alternatives to Utility Pm Workflow Orchestrator?

Skills that share tags, products or a category with Utility Pm Workflow Orchestrator: Agent Workflow (menkesu/awesome-pm-skills, 434 stars), Prod Activation Plan (evolution-foundation/evo-nexus, 545 stars), Rfc Writer (mohitagw15856/pm-claude-skills, 1.4k stars) and Spike (DeL-TaiseiOzaki/claude-code-orchestra, 199 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Utility Pm Workflow Orchestrator?

product-on-purpose (a GitHub organization) maintains it in product-on-purpose/pm-skills, which has 716 GitHub stars. The repository holds 68 skills in this directory. The repository was last updated on October 8, 2026.

Source: product-on-purpose/pm-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.