Applies targeted improvements to an existing pm-skills skill based on feedback, validation reports, or convention changes. Reads current files, previews proposed changes, writes on confirmation, and suggests a version bump.
SkillScore70Maintained
Automatic
◆Product Management pack
Last verified 8/19/2026
What it changes
Passed 14 of 20 test cases with the skill, and 9 of 20 without it.
Without skill43%
With skill70%
Checks it passed that the model alone missed
Recommends utility-pm-skill-builder to create the skill.
Recommends running utility-pm-skill-validate as a next step.
Declines to build the new skill using the iteration workflow.
and 8 more in the full report
7 fixed9 passed either way6 still failing1 broke
Pass-rate lift
+26 pp
Tokens
+190%
Agent turns
0%
Response time
-37%
Measured 8/19/2026v1 · latest is v216 of 23 cases passed with skill · 20 comparable
Tokens, turns and time describe resource use, not a dollar price.
This benchmark measured an earlier version of the skill.
A newer attempt on gemini-3.8-flash on 10/20/2026 did not produce a publishable comparison (not comparable). The snapshot above is the previously measured run.
See it in action
One of 7 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 7
Prompt
We just finished applying edits to skills/a-b-test-design/SKILL.md and updated HISTORY.md. Provide the final completion summary.
What was checked, without and with the skill
Checked
Without skill
With skill
Recommends running utility-pm-skill-validate as a next step.
Missed
Passed
case-23 · gemini-3.6-flash · 8/19/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md300 lines3 files
PM Skill Iterate
This skill improves an existing pm-skills skill by applying targeted changes
based on input you provide. It reads the current skill files, proposes
changes as before/after previews grouped by file, and writes them on your
confirmation. After applying changes, it suggests a version bump class and
offers to update HISTORY.md.
The iterator accepts any of these as input:
A validation report from utility-pm-skill-validate
Direct feedback ("the template is missing section X")
A convention change ("all skills now need a Limitations section")
A general improvement request ("make the example more realistic")
When to Use
After running utility-pm-skill-validate and getting a report with findings
When you have specific feedback on a skill and want to apply it
When a repo convention changes and a skill needs to conform
When a skill's example, template, or instructions need improvement
When iterating on a skill before a release
When NOT to Use
To create a new skill from scratch -> use utility-pm-skill-builder
To audit a skill before making changes -> use utility-pm-skill-validate first
To make bulk convention changes across many skills -> run utility-pm-skill-validate --all first to triage, then iterate one skill at a time
Instructions
When asked to iterate on a skill, follow these steps:
Step 1: Identify the Target Skill
Accept the skill name in any form:
Directory name: deliver-prd
Full path: skills/deliver-prd/SKILL.md
Slash command: deliver-prd
Resolve to the canonical directory path: skills/{name}/.
Run an ordered sequence of pm-skills against one input, pausing for go/no-go and stopping on a failed or empty step. Accepts a saved prioritized action plan (Mode A) or an ad-hoc named chain (Mode B; the chain command routes here). Explicit invocation only; run --dry-run first while the native path is EXPERIMENTAL. To author a durable workflow instead, use utility-pm-workflow-builder.