AF 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.
Guides a contributor from a workflow idea to a complete Workflow Implementation Packet (draft workflow file, draft workflow command, cross-cutting update…
As a process F 45/100 · Will not run — References files that are not bundled: ../utility-pm-workflow-orchestrator/references/PARSE-CONTRACT.md, ../../_workflows/sprint-planning.md, ../../_workflows/customer-discovery.md
How to improve
- The text references files that are not there: add them or drop the references.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 3. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: ../utility-pm-workflow-orchestrator/references/PARSE-CONTRACT.md - warning
missing-refreference to a missing file: ../../_workflows/sprint-planning.md - warning
missing-refreference to a missing file: ../../_workflows/customer-discovery.md - warning
missing-refreference to a missing file: ../../commands/workflow-sprint-planning.md - warning
missing-refreference to a missing file: ../utility-pm-skill-builder/SKILL.md
Process rating: all ten parameters 45/100
- 0Tools and files. 5 referenced file(s) missing: ../utility-pm-workflow-orchestrator/references/PARSE-CONTRACT.md, ../../_workflows/sprint-planning.md, ../../_workflows/customer-discovery.md
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 1 mutating operations with no state check
- 50When it triggers. No condition that starts the skill
- 60Result and completion. Output format stated, no completion criterion
- 100Steps. 36 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1995 tokens
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low The response is described with custom markup (10 tags): a typed call is more reliable
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +2Single-language instructions
- +3Description length 596: enough signal without eating the budget
- +4Structure: 12 headings
- +3Step-by-step instructions: 36 items
- +3Output format is stated explicitly
- +4Has examples (1 code blocks)
- +4Reference files are cited in the instructions (2 of 2)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 80.