[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M727QKYD45K0PCJ591046TK2":3,"skill-same:01M727QKYD45K0PCJ591046TK2":75},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":31,"commitSha":32,"skillDirectory":33,"forksCount":34,"repositoryHtmlUrl":35,"repositoryHomepageUrl":36,"ownerHtmlUrl":37,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":38,"install":39,"resources":52},"01M727QKYD45K0PCJ591046TK2","utility-pm-workflow-orchestrator",null,"Run an ordered sequence of pm-skills against one input, pausing for go\u002Fno-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.","product-on-purpose\u002Fpm-skills","product-on-purpose","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F253892650?v=4","01M7230Q4442AHBADCVFJCS277","Product on Purpose","01M727ASMTF77MQ3AKT3GKRQWM",805,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fproduct-on-purpose\u002Fpm-skills\u002Fblob\u002Fmain\u002Fskills\u002Futility-pm-workflow-orchestrator\u002FSKILL.md",[],[],"2026-11-10 18:39:20",false,"---\nname: utility-pm-workflow-orchestrator\ndescription: Run an ordered sequence of pm-skills against one input, pausing for go\u002Fno-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.\nlicense: Apache-2.0\nmetadata:\n  classification: utility\n  version: \"1.2.0\"\n  updated: 2026-06-10\n  category: workflow\n  frameworks: [triple-diamond]\n  author: product-on-purpose\n---\n\u003C!-- PM-Skills | https:\u002F\u002Fgithub.com\u002Fproduct-on-purpose\u002Fpm-skills | Apache 2.0 -->\n# PM Workflow Orchestrator (Dispatch Skill)\n\nCross-client dispatch wrapper for the `pm-workflow-orchestrator` sub-agent. Detects the runtime; dispatches to the native sub-agent on Claude Code; reads `agents\u002Fpm-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\u002Fno-go by default and stopping on a failed or empty step.\n\n> **Status summary (updated v2.26.0):** smoke-tested on the native Claude Code path; EXPERIMENTAL elsewhere.\n> - **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.\n> - **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.\n>\n> 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](..\u002F..\u002Fsite\u002Fsrc\u002Fcontent\u002Fdocs\u002Freference\u002Fsub-agent-compatibility.md) for the canonical safe-usage matrix.\n\n## When to Use\n\n- You produced a `foundation-prioritized-action-plan` and want to run its runnable Section 7 prompts in order, pausing for go\u002Fno-go (Mode A).\n- 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 \u002Fchain command is the terse front door for this mode.\n- You want a generic runner for a dynamic chain that is NOT a pre-curated `workflow-*` command.\n\nRun modes (orthogonal to client):\n\n- **CHECKPOINTED (default):** pause after each OK step for approve \u002F edit \u002F skip \u002F redo.\n- **GUARDED AUTO (`--auto`, opt-in):** run without pausing on clean steps; still stop on failed, pause on empty, and stay checkpointed for Complex \u002F Chaotic plans unless `--force-auto`.\n\n`--thread` declares a linear dependency so each step receives the prior step's confirmed artifact; see the Mode B Chain Expression Contract in `references\u002FPARSE-CONTRACT.md`.\n\n## When NOT to Use\n\n- 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.\n- 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).\n- You only need to review one artifact -> use `utility-pm-critic`.\n- You want to run library-maintenance machinery as if it were PM work -> the orchestrator refuses Tier-3 maintenance skills.\n- 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.\n\n## Instructions\n\n**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.\n\n### If you are running in Claude Code with the pm-skills plugin installed\n\nInvoke `@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.\n\nThis path is EXPERIMENTAL at v2.24.0 (see Status summary). Instruct the user to run `--dry-run` first.\n\n### If you are running in any other AI client\n\nCodex CLI, Cursor, Windsurf, Copilot CLI, Gemini CLI, or any client without native pm-skills plugin sub-agent support:\n\n1. **Tool-capability pre-flight (FIRST action, before parsing or step 1).** Verify the client can (a) write a file under `_pm-skills\u002Fplan-orchestrator\u002F\u003Crun>\u002F` and (b) run any Bash a downstream skill needs.\n   - 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.\n   - If Bash is unavailable for a step that needs it: surface that step as blocked at its boundary.\n   - Record the detected capabilities; they govern disk-write below.\n2. Read the canonical sub-agent definition at `agents\u002Fpm-workflow-orchestrator.md`.\n3. Read the shared parse and step-status contract at `references\u002FPARSE-CONTRACT.md` (the engine reads the same file; this is what keeps the inline branch and the engine from drifting).\n4. 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.\n5. At each step, read the downstream skill's `SKILL.md` and execute its method inline in this window; classify the return PRODUCED \u002F EMPTY \u002F FAILED with the rubric in `references\u002FPARSE-CONTRACT.md`; write `NN-\u003Cskill-name>.md` to the run directory when disk-write is on.\n6. 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`.\n7. Emit the terminal output (run complete or halted) per the engine's section 4.5.\n\nThe \"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.\n\n## `--dry-run` (readiness probe; run this FIRST on any client)\n\n`--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.\n\n## Cross-Client Notes\n\nBecause non-Claude clients run the loop and every step inline in ONE context window:\n\n1. **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.\n2. **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.\n3. **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).\n\n## Reference Files\n\n- Canonical sub-agent definition: [`agents\u002Fpm-workflow-orchestrator.md`](..\u002F..\u002Fagents\u002Fpm-workflow-orchestrator.md)\n- Shared parse and step-status contract: `references\u002FPARSE-CONTRACT.md`\n- Output template: `references\u002FTEMPLATE.md`\n- Worked example: `references\u002FEXAMPLE.md`\n- Producer (hands plans here in HANDOFF mode): [`skills\u002Ffoundation-prioritized-action-plan\u002FSKILL.md`](..\u002F..\u002Fskills\u002Ffoundation-prioritized-action-plan\u002FSKILL.md)\n- Sub-agent compatibility matrix: [`site\u002Fsrc\u002Fcontent\u002Fdocs\u002Freference\u002Fsub-agent-compatibility.md`](..\u002F..\u002Fsite\u002Fsrc\u002Fcontent\u002Fdocs\u002Freference\u002Fsub-agent-compatibility.md)\n- Runtime components catalog: [`site\u002Fsrc\u002Fcontent\u002Fdocs\u002Freference\u002Fruntime-components.md`](..\u002F..\u002Fsite\u002Fsrc\u002Fcontent\u002Fdocs\u002Freference\u002Fruntime-components.md)\n- Library sample (single checkpointed run): [`library\u002Fsub-agent-samples\u002Fpm-workflow-orchestrator\u002F`](..\u002F..\u002Flibrary\u002Fsub-agent-samples\u002Fpm-workflow-orchestrator\u002F)\n","\u003C!-- PM-Skills | https:\u002F\u002Fgithub.com\u002Fproduct-on-purpose\u002Fpm-skills | Apache 2.0 -->\n# PM Workflow Orchestrator (Dispatch Skill)\n\nCross-client dispatch wrapper for the `pm-workflow-orchestrator` sub-agent. Detects the runtime; dispatches to the native sub-agent on Claude Code; reads `agents\u002Fpm-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\u002Fno-go by default and stopping on a failed or empty step.\n\n> **Status summary (updated v2.26.0):** smoke-tested on the native Claude Code path; EXPERIMENTAL elsewhere.\n> - **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.\n> - **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.\n>\n> 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](..\u002F..\u002Fsite\u002Fsrc\u002Fcontent\u002Fdocs\u002Freference\u002Fsub-agent-compatibility.md) for the canonical safe-usage matrix.\n\n## When to Use\n\n- You produced a `foundation-prioritized-action-plan` and want to run its runnable Section 7 prompts in order, pausing for go\u002Fno-go (Mode A).\n- 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 \u002Fchain command is the terse front door for this mode.\n- You want a generic runner for a dynamic chain that is NOT a pre-curated `workflow-*` command.\n\nRun modes (orthogonal to client):\n\n- **CHECKPOINTED (default):** pause after each OK step for approve \u002F edit \u002F skip \u002F redo.\n- **GUARDED AUTO (`--auto`, opt-in):** run without pausing on clean steps; still stop on failed, pause on empty, and stay checkpointed for Complex \u002F Chaotic plans unless `--force-auto`.\n\n`--thread` declares a linear dependency so each step receives the prior step's confirmed artifact; see the Mode B Chain Expression Contract in `references\u002FPARSE-CONTRACT.md`.\n\n## When NOT to Use\n\n- 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.\n- 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).\n- You only need to review one artifact -> use `utility-pm-critic`.\n- You want to run library-maintenance machinery as if it were PM work -> the orchestrator refuses Tier-3 maintenance skills.\n- 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.\n\n## Instructions\n\n**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.\n\n### If you are running in Claude Code with the pm-skills plugin installed\n\nInvoke `@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.\n\nThis path is EXPERIMENTAL at v2.24.0 (see Status summary). Instruct the user to run `--dry-run` first.\n\n### If you are running in any other AI client\n\nCodex CLI, Cursor, Windsurf, Copilot CLI, Gemini CLI, or any client without native pm-skills plugin sub-agent support:\n\n1. **Tool-capability pre-flight (FIRST action, before parsing or step 1).** Verify the client can (a) write a file under `_pm-skills\u002Fplan-orchestrator\u002F\u003Crun>\u002F` and (b) run any Bash a downstream skill needs.\n   - 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.\n   - If Bash is unavailable for a step that needs it: surface that step as blocked at its boundary.\n   - Record the detected capabilities; they govern disk-write below.\n2. Read the canonical sub-agent definition at `agents\u002Fpm-workflow-orchestrator.md`.\n3. Read the shared parse and step-status contract at `references\u002FPARSE-CONTRACT.md` (the engine reads the same file; this is what keeps the inline branch and the engine from drifting).\n4. 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.\n5. At each step, read the downstream skill's `SKILL.md` and execute its method inline in this window; classify the return PRODUCED \u002F EMPTY \u002F FAILED with the rubric in `references\u002FPARSE-CONTRACT.md`; write `NN-\u003Cskill-name>.md` to the run directory when disk-write is on.\n6. 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`.\n7. Emit the terminal output (run complete or halted) per the engine's section 4.5.\n\nThe \"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.\n\n## `--dry-run` (readiness probe; run this FIRST on any client)\n\n`--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.\n\n## Cross-Client Notes\n\nBecause non-Claude clients run the loop and every step inline in ONE context window:\n\n1. **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.\n2. **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.\n3. **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).\n\n## Reference Files\n\n- Canonical sub-agent definition: [`agents\u002Fpm-workflow-orchestrator.md`](..\u002F..\u002Fagents\u002Fpm-workflow-orchestrator.md)\n- Shared parse and step-status contract: `references\u002FPARSE-CONTRACT.md`\n- Output template: `references\u002FTEMPLATE.md`\n- Worked example: `references\u002FEXAMPLE.md`\n- Producer (hands plans here in HANDOFF mode): [`skills\u002Ffoundation-prioritized-action-plan\u002FSKILL.md`](..\u002F..\u002Fskills\u002Ffoundation-prioritized-action-plan\u002FSKILL.md)\n- Sub-agent compatibility matrix: [`site\u002Fsrc\u002Fcontent\u002Fdocs\u002Freference\u002Fsub-agent-compatibility.md`](..\u002F..\u002Fsite\u002Fsrc\u002Fcontent\u002Fdocs\u002Freference\u002Fsub-agent-compatibility.md)\n- Runtime components catalog: [`site\u002Fsrc\u002Fcontent\u002Fdocs\u002Freference\u002Fruntime-components.md`](..\u002F..\u002Fsite\u002Fsrc\u002Fcontent\u002Fdocs\u002Freference\u002Fruntime-components.md)\n- Library sample (single checkpointed run): [`library\u002Fsub-agent-samples\u002Fpm-workflow-orchestrator\u002F`](..\u002F..\u002Flibrary\u002Fsub-agent-samples\u002Fpm-workflow-orchestrator\u002F)\n",{"name":5,"license":15,"metadata":24,"description":7},{"author":9,"updated":25,"version":26,"category":27,"frameworks":28,"classification":30},1781049600000,"1.2.0","workflow",[29],"triple-diamond","utility","main","9b920db418c5bf641edea9afb4915a286e1d42ea","skills\u002Futility-pm-workflow-orchestrator",102,"https:\u002F\u002Fgithub.com\u002Fproduct-on-purpose\u002Fpm-skills","https:\u002F\u002Fproduct-on-purpose.github.io\u002Fpm-skills\u002F","https:\u002F\u002Fgithub.com\u002Fproduct-on-purpose","2026-11-14 16:57:35",{"source":8,"skillName":5,"commands":40,"prompt":50,"zipAvailable":51},[41,44,47],{"tool":42,"command":43},"npx","npx skills add product-on-purpose\u002Fpm-skills --skill utility-pm-workflow-orchestrator",{"tool":45,"command":46},"bunx","bunx skills add product-on-purpose\u002Fpm-skills --skill utility-pm-workflow-orchestrator",{"tool":48,"command":49},"pnpm","pnpm dlx skills add product-on-purpose\u002Fpm-skills --skill utility-pm-workflow-orchestrator","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fproduct-on-purpose\u002Fpm-skills\u002Fblob\u002Fmain\u002Fskills\u002Futility-pm-workflow-orchestrator\u002FSKILL.md",true,[53,59,63,67,71],{"path":54,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":57,"sourceHtmlUrl":58},"evals\u002Ftrigger-fixtures.json","REFERENCE","参考文档",6644,"https:\u002F\u002Fgithub.com\u002Fproduct-on-purpose\u002Fpm-skills\u002Fblob\u002Fmain\u002Fskills\u002Futility-pm-workflow-orchestrator\u002Fevals\u002Ftrigger-fixtures.json",{"path":60,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":61,"sourceHtmlUrl":62},"HISTORY.md",1512,"https:\u002F\u002Fgithub.com\u002Fproduct-on-purpose\u002Fpm-skills\u002Fblob\u002Fmain\u002Fskills\u002Futility-pm-workflow-orchestrator\u002FHISTORY.md",{"path":64,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":65,"sourceHtmlUrl":66},"references\u002FEXAMPLE.md",6724,"https:\u002F\u002Fgithub.com\u002Fproduct-on-purpose\u002Fpm-skills\u002Fblob\u002Fmain\u002Fskills\u002Futility-pm-workflow-orchestrator\u002Freferences\u002FEXAMPLE.md",{"path":68,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":69,"sourceHtmlUrl":70},"references\u002FPARSE-CONTRACT.md",9152,"https:\u002F\u002Fgithub.com\u002Fproduct-on-purpose\u002Fpm-skills\u002Fblob\u002Fmain\u002Fskills\u002Futility-pm-workflow-orchestrator\u002Freferences\u002FPARSE-CONTRACT.md",{"path":72,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":73,"sourceHtmlUrl":74},"references\u002FTEMPLATE.md",4059,"https:\u002F\u002Fgithub.com\u002Fproduct-on-purpose\u002Fpm-skills\u002Fblob\u002Fmain\u002Fskills\u002Futility-pm-workflow-orchestrator\u002Freferences\u002FTEMPLATE.md",[76,83,90,97,104,111],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M727QTD4J5TPP3EEYPXMGZE4","utility-update-pm-skills","Checks for newer pm-skills releases, compares local vs. latest version, previews what would change, and updates local files after user confirmation. Generates a structured update report documenting changed files, new capabilities, and the value delta between versions. Use when you want to bring a local pm-skills installation up to date.","https:\u002F\u002Fgithub.com\u002Fproduct-on-purpose\u002Fpm-skills\u002Fblob\u002Fmain\u002Fskills\u002Futility-update-pm-skills\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M727QQSXYBZK7D29C80WMQ8M","utility-slideshow-creator","Generates professional presentations from a JSON deck specification using 18 slide types with dark\u002Flight variants, content-to-layout decision logic, and calibrated character limits. Ships with a default professional theme.","https:\u002F\u002Fgithub.com\u002Fproduct-on-purpose\u002Fpm-skills\u002Fblob\u002Fmain\u002Fskills\u002Futility-slideshow-creator\u002FSKILL.md",[],[],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":19},"01M727QFN6W9M8JGVXNQMT5642","utility-pm-workflow-builder","Guides a contributor from a workflow idea to a complete Workflow Implementation Packet (draft workflow file, draft workflow command, cross-cutting update checklist) in a staging area for review. Runs overlap analysis against the existing workflows with a Why Gate, then helps select and sequence skills with authored handoffs. Use when creating a new multi-skill workflow or promoting a repeated ad-hoc chain into a durable one. To build a single skill instead, use utility-pm-skill-builder; to run a sequence without authoring anything, use the chain command or utility-pm-workflow-orchestrator.","https:\u002F\u002Fgithub.com\u002Fproduct-on-purpose\u002Fpm-skills\u002Fblob\u002Fmain\u002Fskills\u002Futility-pm-workflow-builder\u002FSKILL.md",[],[],{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":19},"01M727QCDS2WFTJPHXASSE5W6X","utility-pm-skill-validate","Audits an existing pm-skills skill against structural conventions and quality criteria. Produces a structured validation report with pass\u002Ffail checks, severity-graded findings, and actionable recommendations. Use when checking whether a skill meets repo standards before shipping or after making changes.","https:\u002F\u002Fgithub.com\u002Fproduct-on-purpose\u002Fpm-skills\u002Fblob\u002Fmain\u002Fskills\u002Futility-pm-skill-validate\u002FSKILL.md",[],[],{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":110,"publishedAt":19},"01M727Q8GW1AZWPNWXYH7WHG9F","utility-pm-skill-iterate","Applies targeted improvements to an existing pm-skills skill based on feedback, validation reports, or convention changes. Reads current files, previews proposed changes, writes on confirmation, and suggests a version bump. Use when improving a skill after validation or feedback.","https:\u002F\u002Fgithub.com\u002Fproduct-on-purpose\u002Fpm-skills\u002Fblob\u002Fmain\u002Fskills\u002Futility-pm-skill-iterate\u002FSKILL.md",[],[],{"skillNo":112,"name":113,"nameZh":6,"description":114,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":115,"categories":116,"keywords":117,"publishedAt":19},"01M727Q49TZERFYHQJTT8DCRK0","utility-pm-skill-builder","Guides contributors from a PM skill idea to a complete Skill Implementation Packet aligned with pm-skills conventions. Runs gap analysis, validates through a Why Gate, classifies by type and phase, generates draft files, and writes to a staging area for review before promotion.","https:\u002F\u002Fgithub.com\u002Fproduct-on-purpose\u002Fpm-skills\u002Fblob\u002Fmain\u002Fskills\u002Futility-pm-skill-builder\u002FSKILL.md",[],[]]