Stats
Actions
Tags
From pm-skills
Parses a chain expression and context from user input, then dispatches an ordered chain of pm-skills to the workflow orchestrator engine with shared context and optional flags.
How this command is triggered — by the user, by Claude, or both
Slash command
/pm-skills:chainThe summary Claude sees in its command listing — used to decide when to auto-load this command
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 noth...
Run an ad-hoc chain of pm-skills in the order given, passing the shared context to every step.
$ARGUMENTS carries a chain expression followed by free-form context.
--auto, --force-auto, --dry-run, --thread., 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.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).
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).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
npx claudepluginhub product-on-purpose/pm-skills --plugin pm-skills/command-pipelineExecutes a pipeline of commands from a specification string, supporting conditions, iterations, variables, error handling, retries, and parallel branches.
/planAnalyzes a task description, classifies its type (feature, bugfix, etc.), and generates a minimum-viable pipeline plan with ordered steps, dependencies, and done criteria. For multi-layer features, produces vertical slice tables with worker assignments.
/ns-workflowRoutes user intents to the appropriate phase-pipeline skill — discuss, spec, plan, execute, verify, add tests, and more. Supports autonomous, fast, and MVP modes.
/sc-workflowGenerates structured implementation workflows from PRDs or feature descriptions using multi-persona coordination. Supports --strategy, --depth, and --parallel options.
/orchestrateOrchestrates PACT specialist agents for a task by creating full task hierarchy with PREPARE, ARCHITECT, CODE, TEST phases, dependency chains, agent spawning, and completion monitoring.