From polymath-flows
Run a flows-lite workflow end-to-end; the skill drives the loop while bin/polymath-flow owns YAML validation, state, and mustPass checks.
How this skill is triggered — by the user, by Claude, or both
Slash command
/polymath-flows:run-workflowThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
> Drive a flows-lite workflow from start to completion. This skill is the human-facing presenter; the deterministic state machine lives in `${CLAUDE_PLUGIN_ROOT}/bin/polymath-flow`.
Drive a flows-lite workflow from start to completion. This skill is the human-facing presenter; the deterministic state machine lives in
${CLAUDE_PLUGIN_ROOT}/bin/polymath-flow.
/polymath-flows:run-workflow <name> ....shipFeature is the appropriate workflow.shipFeature.key=value (e.g. title="Rate-limit /login", scope=small).Start the run. Execute:
${CLAUDE_PLUGIN_ROOT}/bin/polymath-flow start <name> --input key=value [--input key=value ...]
Parse the returned run_id. If the executable reports validation errors, surface them and stop.
Loop until the workflow completes or pauses. For each iteration:
a. Ask the executable for the next step:
${CLAUDE_PLUGIN_ROOT}/bin/polymath-flow next <run_id>
The output JSON contains step_id, invoke (routing label), prompt, and any expected artifacts.
b. Announce the step to the user with one sentence: "Step of : <step_id> — ".
c. Perform the work for this step in the current turn, guided by the invoke capability label. For v0.1, invoke is a routing label, not a programmatic slash-command call: treat it as guidance about which skill's procedure to follow (e.g. polymath-product:prd → use the prd skill from polymath-product).
d. Write any declared artifacts to disk.
e. Compose a one-paragraph step summary describing what changed and pointing to files. Save to a temporary file and tell the executable:
${CLAUDE_PLUGIN_ROOT}/bin/polymath-flow complete <run_id> <step_id> --summary <summary-file>
The summary must include the words "test", "tests", "verified", or "verification" for the verify step so the shipFeature workflow's stepSummaryMatches check passes.
f. If a step fails or the user wants to pause, run:
${CLAUDE_PLUGIN_ROOT}/bin/polymath-flow fail <run_id> <step_id> --summary <reason>
Then stop the loop and report.
Assert. After all steps are complete, run:
${CLAUDE_PLUGIN_ROOT}/bin/polymath-flow assert <run_id>
This evaluates all mustPass checks. If any fail, the workflow is paused; report the failures and stop. The user can resume with /polymath-flows:resume-workflow <run_id> after addressing them.
completed or paused with mustPass failure summary.invoke as a slash-command call. It is a label.complete without writing the declared artifacts.artifacts for a step unless the workflow step's prompt explicitly authorizes it.npx claudepluginhub mohammadbafkar/polymath --plugin polymath-flowsGuides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.