utility-pm-skill-iterate

Pass the validation report from utility-pm-skill-validate to this Skill along with the target skill name. It parses the Recommendations section, builds an intended-changes list, previews each edit, and writes only after your confirmation.

Describe the convention change and name the target skill, for example adding a Limitations section. The Skill maps the change to specific files and sections, shows before/after previews, and applies the edit on confirmation.

Run utility-pm-skill-validate first to audit a skill and produce findings, then use this Skill to apply the recommended changes. Iteration is for editing; validation is for auditing without modifying files.

No. It suggests a SemVer bump class (patch, minor, or major) with reasoning based on whether the change clarifies, adds optional capability, or breaks the required contract. The version is written only after you explicitly confirm.

A stale-preview guard re-reads each target file before writing and compares it to the content recorded earlier. If anything changed, no files are written and the preview is regenerated from the current content.

HISTORY.md is created only when a skill ships its second version, with entries for both versions. It is not created for a first-version skill, and existing files are format-validated before appending new entries.