Menu
Analyze weft workflow runs for timing and friction. Use only when user types /wf-analyze.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Query the weft event log with filters. Use only when user types /ev-query.
Check weft template currency — drift of working copies vs the bundled canonical, and whether the plugin clone is behind upstream. Use only when user types /wf-doctor.
Resume a weft workflow parked in 'waiting' at a human gate (unattended on_fail=block). Use only when user types /wf-resume.
Execute the current weft step via the Claude Code Workflow tool, then auto-transition on the structured verdict. Use only when user types /wf-run-step, or when advancing a step whose template declares an executor.
Initialize a weft workflow from a template or inline steps. Use only when user types /wf-start.
Create a new weft workflow template or edit an existing one interactively. Use only when user types /wf-template.
| name | wf-analyze |
| description | Analyze weft workflow runs for timing and friction. Use only when user types /wf-analyze. |
| argument-hint | [--template NAME] |
| allowed-tools | ["Bash","Read"] |
Read-only. Aggregates the event log into per-template metrics and surfaces recurring friction.
$ARGUMENTS
Run:
python3 "${CLAUDE_PLUGIN_ROOT}/core/cli.py" analyze $ARGUMENTS
With no arguments, it reports across all templates. Pass --template NAME to scope to one.
Present results in a readable format, not raw JSON.
workflow-qa.jsonl/wf-analyze — metrics across all templates/wf-analyze --template feature-workflow — scope to one template