SKILL

Chain

Run an ad-hoc ordered chain of pm-skills with shared context (ephemeral; routes to the pm-workflow-orchestrator)

Published by @product-on-purpose·0 agent reads / 30d·0 saves·

Run an ad-hoc chain of pm-skills in the order given, passing the shared context to every step.

Parse the input

$ARGUMENTS carries a chain expression followed by free-form context.

  1. Extract flags first, wherever they appear: --auto, --force-auto, --dry-run, --thread.
  2. The chain expression is exactly the leading separator-joined list of skill names (, and -> equivalent; mixing allowed). It ends after the first name that is NOT followed by a separator; everything after that is the context, even when the context words look like skill names. A trailing separator with nothing after it is an error to surface, not to guess around.
  3. Everything after the chain expression is the context. This command parses the BOUNDARY only; all skill-name validation belongs to the engine.

Examples: /chain define-problem-statement -> define-hypothesis --thread Mobile checkout drop-off runs two steps with --thread, context "Mobile checkout drop-off". Lowercase context is fine: /chain deliver-prd, deliver-user-stories mobile checkout redesign is two steps with context "mobile checkout redesign" (the boundary is the missing separator after deliver-user-stories, not the letter case).

Confirm and dispatch

  1. Restate in one line: the parsed steps in order, the flags, and the context.
  2. Invoke the utility-pm-workflow-orchestrator skill from skills/utility-pm-workflow-orchestrator/SKILL.md with that chain, context, and flags (a Mode B run). The engine validates every name pre-flight and owns all run rules; this command adds none. The grammar lives in skills/utility-pm-workflow-orchestrator/references/PARSE-CONTRACT.md (Mode B Chain Expression Contract).
  3. Relay the engine's per-step blocks and terminal output, including the promotion suggestion for reusable chains.

Nothing is persisted beyond the engine's own gitignored run artifacts. To make a chain durable, follow the completion suggestion to utility-pm-workflow-builder. While the native engine path is EXPERIMENTAL, recommend --dry-run first.

Context from user: $ARGUMENTS

Bundled with this artifact

2 files

Reference files that ship alongside this artifact. Agents pull these in only when the task needs them.

More on the bench

SKILL▲0

Pptx

Use this skill any time a .pptx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx file (even if the extracted content will be used elsewhere, like in an email or summary); editing, modifying, or updating existing presentations; combining or splitting slide files; working with templates, layouts, speaker notes, or comments. Trigger whenever the user mentions "deck," "slides," "presentation," or references a .pptx filename, regardless of what they plan to do with the content afterward. If a .pptx file needs to be opened, created, or touched, use this skill.

w95
product-management+1
⊙ 0
SKILL▲0

Knowledge Management

Write and maintain knowledge base articles from resolved support issues. Use when a ticket has been resolved and the solution should be documented, when updating existing KB articles, or when creating how-to guides, troubleshooting docs, or FAQ entries.

w95
customer-success+2
⊙ 0
SKILL▲0

Customer Research

Research customer questions by searching across documentation, knowledge bases, and connected sources, then synthesize a confidence-scored answer. Use when a customer asks a question you need to investigate, when building background on a customer situation, or when you need account context.

w95
customer-success+1
⊙ 0