[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M727QTD4J5TPP3EEYPXMGZE4":3,"skill-same:01M727QTD4J5TPP3EEYPXMGZE4":71},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":31,"commitSha":32,"skillDirectory":33,"forksCount":34,"repositoryHtmlUrl":35,"repositoryHomepageUrl":36,"ownerHtmlUrl":37,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":38,"install":39,"resources":52},"01M727QTD4J5TPP3EEYPXMGZE4","utility-update-pm-skills",null,"Checks for newer pm-skills releases, compares local vs. latest version, previews what would change, and updates local files after user confirmation. Generates a structured update report documenting changed files, new capabilities, and the value delta between versions. Use when you want to bring a local pm-skills installation up to date.","product-on-purpose\u002Fpm-skills","product-on-purpose","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F253892650?v=4","01M7230Q4442AHBADCVFJCS277","Product on Purpose","01M727ASMTF77MQ3AKT3GKRQWM",805,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fproduct-on-purpose\u002Fpm-skills\u002Fblob\u002Fmain\u002Fskills\u002Futility-update-pm-skills\u002FSKILL.md",[],[],"2026-11-10 18:39:20",false,"---\nname: utility-update-pm-skills\ndescription: Checks for newer pm-skills releases, compares local vs. latest version, previews what would change, and updates local files after user confirmation. Generates a structured update report documenting changed files, new capabilities, and the value delta between versions. Use when you want to bring a local pm-skills installation up to date.\nlicense: Apache-2.0\nmetadata:\n  classification: utility\n  version: \"1.0.1\"\n  updated: 2026-07-04\n  category: coordination\n  frameworks: [triple-diamond]\n  author: product-on-purpose\n---\n\u003C!-- PM-Skills | https:\u002F\u002Fgithub.com\u002Fproduct-on-purpose\u002Fpm-skills | Apache 2.0 -->\n\n# PM Skills Updater\n\nThis skill updates a local pm-skills installation to the latest public\nrelease. It validates connectivity, compares versions, previews changes,\nand produces a structured report documenting what was updated and what\nnew capabilities are available.\n\n## When to Use\n\n- When you want to update local pm-skills to the latest release\n- When you want to check if a newer version is available\n- After a new pm-skills release is announced\n- When onboarding and you want to confirm you have the latest version\n\n## When NOT to Use\n\n- To create or edit individual skills -> use `utility-pm-skill-builder` or `utility-pm-skill-iterate`\n- To validate skills against conventions -> use `utility-pm-skill-validate`\n- If you are a maintainer working directly on the pm-skills repo (use git)\n- To pin a specific older version (this skill always targets the latest release)\n\n## Flags\n\n| Flag | Behavior |\n|------|----------|\n| *(none)* | Full update flow: pre-flight → preview → confirm → update → report |\n| `--report-only` | Pre-flight → preview → report (no files written) |\n| `--status` | Lightweight version check - prints current and latest version, then stops |\n\n### --status behavior\n\nWhen `--status` is provided, run only the pre-flight checks and display:\n\n```\npm-skills v{local} (installed, from {source})\npm-skills v{latest} (latest, released {date})\n{Status: up to date | update available ({type})}\n\nRun utility-update-pm-skills for details, or utility-update-pm-skills --report-only for a preview.\n```\n\nNo report file is generated. No files are written.\n\n## Instructions\n\nWhen asked to update pm-skills (without `--status`), follow these steps:\n\n### Step 1: Pre-Flight\n\nRun three checks before proceeding:\n\n1. **Network access**: Reach the GitHub API or repository URL\n   (`https:\u002F\u002Fgithub.com\u002Fproduct-on-purpose\u002Fpm-skills`). Use any\n   available method: `curl`, `wget`, GitHub CLI (`gh`), or MCP tools.\n\n2. **Latest version**: Query the latest release using this fallback chain\n   (try each in order, use the first that succeeds):\n   1. GitHub API: `GET \u002Frepos\u002Fproduct-on-purpose\u002Fpm-skills\u002Freleases\u002Flatest`\n   2. GitHub CLI: `gh release list --repo product-on-purpose\u002Fpm-skills --limit 1`\n   3. Git: `git ls-remote --tags https:\u002F\u002Fgithub.com\u002Fproduct-on-purpose\u002Fpm-skills.git`\n\n   If all three fail (rate limiting, 404, malformed response, no network),\n   enter degraded mode (see below).\n\n   Record: version string, release date, release notes URL, release notes body.\n\n3. **Local version**: Read from the first available source:\n   - `.claude-plugin\u002Fplugin.json` → `version` field\n   - `marketplace.json` → `plugins[0].version` field\n   - `CHANGELOG.md` → most recent version header\n   - Git tags → most recent `v*` tag\n\n   **Version parsing:** Normalize by stripping an optional `v` prefix and\n   trimming whitespace. If a source is present but yields an empty,\n   non-semver, or malformed string (invalid JSON, missing field), skip it\n   with a warning and try the next source. Only fall back to `0.0.0`\n   after all four sources fail.\n\n**If network access fails** (degraded mode):\n- Report the failure with error details.\n- Provide manual update instructions:\n  > Visit https:\u002F\u002Fgithub.com\u002Fproduct-on-purpose\u002Fpm-skills\u002Freleases to\n  > download the latest release. Extract the archive and copy the\n  > `skills\u002F`, `commands\u002F`, `_workflows\u002F`, and other content directories\n  > to your local pm-skills installation.\n- Stop execution.\n\n### Step 2: Version Comparison\n\nCompare the local version against the latest release using semver.\n\n**If local version >= latest version:**\n- Report: \"Your pm-skills installation is up to date (v{local}).\"\n- Offer to generate a report-only anyway.\n- Stop execution.\n\n**If local version \u003C latest version:**\n- Show the version delta:\n  ```\n  Local version:  v{local}\n  Latest version: v{latest}\n  Update type:    {major | minor | patch}\n  ```\n- **Major version warning**: If the update is a major bump (e.g., v2.x\n  to v3.x), show a prominent warning:\n  > This is a major version update. It may include breaking changes to\n  > skill contracts. Review the release notes before proceeding.\n- Continue to Step 3.\n\n### Step 3: Preview\n\nShow the user what the update includes:\n\n1. **Version delta**: local version, latest version, update type.\n\n2. **Value summary**: Derive from CHANGELOG entries between the two\n   versions, GitHub release notes, and directory diffs (new skills\u002F,\n   new _workflows\u002F files):\n   - New skills and what they enable\n   - Updated skills and what improved\n   - New workflows and what they connect\n   - Other notable changes\n\n3. **File manifest**: List of files and folders that will be written,\n   grouped by directory with counts:\n   ```\n   Files to be written:\n     skills\u002F       31 files (2 new, 29 updated)\n     commands\u002F     38 files (2 new, 36 updated)\n     _workflows\u002F    9 files (1 new, 8 updated)\n     other          7 files\n     Total:        85 files\n   ```\n\n**If `--report-only`:** Generate the report using `references\u002FTEMPLATE.md`\nwith the banner \"Report only - update was not applied.\" Save to\n`_pm-skills\u002Fupdates\u002Fupdate-report_v{latest}_report-only_{YYYY-MM-DD_HHMMSS}.md`. Stop\nexecution.\n\n### Step 4: Confirmation\n\nPrompt the user for two decisions:\n\n1. **Update confirmation**:\n   \"These files will be overwritten. Proceed? [yes \u002F no]\"\n   - If major version bump: require typing \"yes\" explicitly.\n   - If the user declines: save a report-only and stop.\n\n2. **Backup offer**:\n   \"Create a backup of current files before updating?\n   [yes (recommended) \u002F no]\"\n   - If yes: copy all in-scope files to\n     `_pm-skills\u002Fbackups\u002Fv{current}_{YYYY-MM-DD_HHMMSS}\u002F`\n   - Create the `_pm-skills\u002F` directory if it doesn't exist.\n\n### Step 5: Update\n\nExecute the update using validated-before-copy with backup:\n\n1. **Download**: Fetch the release ZIP asset (`pm-skills-vX.Y.Z.zip`)\n   from the GitHub Release page to a temporary directory. This is the\n   curated build artifact produced by `build-release.sh` - it includes\n   only user-facing content and excludes `docs\u002Finternal\u002F`.\n\n2. **Validate**: Confirm the extracted archive contains `skills\u002F`,\n   `commands\u002F`, `AGENTS.md`, and `.claude-plugin\u002Fplugin.json`. If\n   validation fails, report the error and stop without writing any files.\n\n3. **Copy**: Overwrite in-scope files from the extracted archive to the\n   install root. Show progress per directory:\n   ```\n   Updating pm-skills v2.9.0 -> v2.10.0...\n     skills\u002F       31\u002F31 ████████████████████  done\n     commands\u002F     38\u002F38 ████████████████████  done\n     _workflows\u002F    9\u002F9  ████████████████████  done\n     other files    7\u002F7  ████████████████████  done\n   ```\n\n4. **Clean up**: Remove the temporary directory.\n\n### Step 6: Post-Update\n\n1. **Smoke test**:\n   - Version consistency: `plugin.json`, `marketplace.json`, and\n     `CHANGELOG.md` all reflect the new version. (Note: version detection\n     in Step 1 uses first-match; the smoke test verifies all sources\n     agree. A mismatch here suggests a release packaging issue.)\n   - File integrity: `AGENTS.md`, `skills\u002F`, `commands\u002F`, `_workflows\u002F`\n     all exist.\n   - Skill count delta: count skills before and after, report the change.\n   - If any check fails: warn the user with specific details. Do NOT\n     auto-rollback. Provide recovery guidance:\n     - **Version mismatch**: \"Run the update again, or manually edit\n       {file} to set the version to {expected}.\"\n     - **Missing files**: \"Re-run `utility-update-pm-skills` to re-download,\n       or restore from backup: `cp -r _pm-skills\u002Fbackups\u002F{dir}\u002F* .`\"\n     - **If backup exists**: Always remind the user of the backup\n       location and restore command.\n\n2. **Summary line**: Show a single scannable confirmation:\n   ```\n   Updated v{old} -> v{new} | +{n} skills, +{n} workflows | Report: _pm-skills\u002Fupdates\u002F{file}\n   ```\n\n3. **Completion report**: Generate using `references\u002FTEMPLATE.md` and\n   save to `_pm-skills\u002Fupdates\u002Fupdate-report_v{from}-to-v{to}_{YYYY-MM-DD_HHMMSS}.md`\n\n4. **MCP advisory**: If `..\u002Fpm-skills-mcp\u002F` exists, try to read\n   `pm-skills-source.json`. If the file is missing or malformed, show:\n   \"pm-skills-mcp detected but pm-skills-source.json not found or\n   unreadable. Check the MCP repo manually.\" If readable, show:\n   ```\n   pm-skills-mcp detected at ..\u002Fpm-skills-mcp\u002F\n     Embedded skills version: v{embedded}\n     Updated pm-skills version: v{new}\n\n     To update the MCP server's embedded skills:\n       cd ..\u002Fpm-skills-mcp && npm run embed-skills && npm run build\n   ```\n\n5. **Next steps**:\n   ```\n   Next Steps:\n   - Review the update report at _pm-skills\u002Fupdates\u002F{report-file}\n   - Run utility-pm-skill-validate --all to verify skill integrity\n   - Run local CI: bash scripts\u002Flint-skills-frontmatter.sh\n   - Check release notes: {release-url}\n   ```\n\n## File Scope\n\nThe updater writes only files present in the release ZIP asset\n(`pm-skills-vX.Y.Z.zip`), which is the curated build produced by\n`build-release.sh`. As of v2.30.0 the ZIP also carries the `agents\u002F`\nsub-agent definitions and the `hooks\u002F` activation hooks, so a ZIP install\nhas the runtime files the dispatch skills reference. The ZIP excludes\n`docs\u002Finternal\u002F` and other non-user-facing content - no exclusion logic is\nneeded at copy time.\n\n**Files included in the release ZIP (updated):**\n\n| Path | Rationale |\n|------|-----------|\n| `skills\u002F` | Core skill files |\n| `commands\u002F` | Slash command definitions |\n| `_workflows\u002F` | Workflow chains |\n| `agents\u002F` | Sub-agent definitions the `utility-pm-*` dispatch skills read at runtime |\n| `hooks\u002F` | Activation hooks (guardrails + phase router) including `hooks.json` |\n| `library\u002F` | Sample library and skill output samples (note: user-added samples may be overwritten) |\n| `AGENTS.md` | Skill discovery for IDEs |\n| `.claude-plugin\u002Fplugin.json` | Version + plugin metadata |\n| `marketplace.json` | Marketplace metadata |\n| `CHANGELOG.md` | Release history |\n| `README.md` | Public docs |\n| `docs\u002F` (public guides, reference, workflows) | User-facing documentation |\n| `scripts\u002F` | CI\u002Fvalidation scripts |\n| `mkdocs.yml` | Docs site config |\n\n**Files NOT in the release ZIP (never overwritten):**\n\n| Path | Rationale |\n|------|-----------|\n| `docs\u002Finternal\u002F` | Excluded from ZIP by `build-release.sh` |\n| `_NOTES\u002F` | Local-only, gitignored, not in ZIP |\n| `_pm-skills\u002F` | Local state (reports, backups), not in ZIP |\n| `.github\u002F` | CI workflows, not in ZIP |\n| `CONTRIBUTING.md`, `LICENSE` | Not in ZIP (repo-level files) |\n\n## Output Contract\n\nThe skill MUST:\n- Validate network access before any remote operations\n- Show a preview before writing any files\n- Require explicit user confirmation before overwriting\n- Offer a backup before overwriting\n- Use validated-before-copy (download to temp, validate, then copy; backup is the recovery path for mid-copy failures)\n- Generate a report in both modes (report-only and completion)\n- Run the post-update smoke test\n- Show MCP advisory if sibling repo is detected\n\nThe skill MUST NOT:\n- Write files without user confirmation\n- Proceed without network access confirmation\n- Modify files outside the pm-skills directory\n- Modify `docs\u002Finternal\u002F`, `_NOTES\u002F`, or `_pm-skills\u002F` with upstream content\n- Auto-rollback on smoke test failure (inform the user instead)\n- Delete local files that don't exist in the upstream release\n\n## Quality Checklist\n\nBefore marking the update complete, verify:\n\n- [ ] Pre-flight passed: network, versions detected\n- [ ] User was shown preview before any files were written\n- [ ] User explicitly confirmed before update proceeded\n- [ ] Backup was offered (and created if accepted)\n- [ ] Archive was downloaded to temp and validated before copying\n- [ ] All in-scope files were written successfully\n- [ ] Version consistency: plugin.json, marketplace.json, CHANGELOG match\n- [ ] File integrity: AGENTS.md, skills\u002F, commands\u002F, _workflows\u002F exist\n- [ ] Skill count delta is reported (before -> after)\n- [ ] Report was generated and saved to `_pm-skills\u002Fupdates\u002F`\n- [ ] MCP advisory was shown if sibling repo detected\n- [ ] Next steps were presented\n- [ ] Summary line displayed\n\n## FAQ\n\n**I'm a contributor who cloned the repo. Should I use this skill?**\nNo. Use `git pull` or `git fetch && git merge` instead. This skill is\nfor end users who installed pm-skills as a plugin or downloaded a release.\n\n**Can I update to a specific version instead of the latest?**\nNot in v1. This skill always targets the latest release. To install a\nspecific version, download it manually from the releases page.\n\n**What happens to my local notes and planning docs?**\nThey are never touched. The skill explicitly excludes `docs\u002Finternal\u002F`,\n`_NOTES\u002F`, and `_pm-skills\u002F` from updates. See the File Scope table.\n\n**What happens to files I added that aren't in the upstream release?**\nThey are left untouched. The skill only overwrites files that exist in\nthe new release - it never deletes local files.\n\n**How do I undo an update?**\nIf you created a backup (the default offer), restore it:\n`cp -r _pm-skills\u002Fbackups\u002Fv{version}_{timestamp}\u002F* .`\nIf you didn't create a backup but have git, use `git checkout .` to\nrestore tracked files to their last committed state.\n\n**The update failed partway through. What do I do?**\nThe skill validates before copying (download to temp, check, then write),\nso partial failures are rare. If it does happen: restore from backup if\navailable, or re-run `utility-update-pm-skills` to retry.\n\n## Further Reading\n\nFor a visual walkthrough and additional context, see the\n[Updating PM Skills Guide](..\u002F..\u002Fsite\u002Fsrc\u002Fcontent\u002Fdocs\u002Fguides\u002Fupdating-pm-skills.md).\n","\u003C!-- PM-Skills | https:\u002F\u002Fgithub.com\u002Fproduct-on-purpose\u002Fpm-skills | Apache 2.0 -->\n\n# PM Skills Updater\n\nThis skill updates a local pm-skills installation to the latest public\nrelease. It validates connectivity, compares versions, previews changes,\nand produces a structured report documenting what was updated and what\nnew capabilities are available.\n\n## When to Use\n\n- When you want to update local pm-skills to the latest release\n- When you want to check if a newer version is available\n- After a new pm-skills release is announced\n- When onboarding and you want to confirm you have the latest version\n\n## When NOT to Use\n\n- To create or edit individual skills -> use `utility-pm-skill-builder` or `utility-pm-skill-iterate`\n- To validate skills against conventions -> use `utility-pm-skill-validate`\n- If you are a maintainer working directly on the pm-skills repo (use git)\n- To pin a specific older version (this skill always targets the latest release)\n\n## Flags\n\n| Flag | Behavior |\n|------|----------|\n| *(none)* | Full update flow: pre-flight → preview → confirm → update → report |\n| `--report-only` | Pre-flight → preview → report (no files written) |\n| `--status` | Lightweight version check - prints current and latest version, then stops |\n\n### --status behavior\n\nWhen `--status` is provided, run only the pre-flight checks and display:\n\n```\npm-skills v{local} (installed, from {source})\npm-skills v{latest} (latest, released {date})\n{Status: up to date | update available ({type})}\n\nRun utility-update-pm-skills for details, or utility-update-pm-skills --report-only for a preview.\n```\n\nNo report file is generated. No files are written.\n\n## Instructions\n\nWhen asked to update pm-skills (without `--status`), follow these steps:\n\n### Step 1: Pre-Flight\n\nRun three checks before proceeding:\n\n1. **Network access**: Reach the GitHub API or repository URL\n   (`https:\u002F\u002Fgithub.com\u002Fproduct-on-purpose\u002Fpm-skills`). Use any\n   available method: `curl`, `wget`, GitHub CLI (`gh`), or MCP tools.\n\n2. **Latest version**: Query the latest release using this fallback chain\n   (try each in order, use the first that succeeds):\n   1. GitHub API: `GET \u002Frepos\u002Fproduct-on-purpose\u002Fpm-skills\u002Freleases\u002Flatest`\n   2. GitHub CLI: `gh release list --repo product-on-purpose\u002Fpm-skills --limit 1`\n   3. Git: `git ls-remote --tags https:\u002F\u002Fgithub.com\u002Fproduct-on-purpose\u002Fpm-skills.git`\n\n   If all three fail (rate limiting, 404, malformed response, no network),\n   enter degraded mode (see below).\n\n   Record: version string, release date, release notes URL, release notes body.\n\n3. **Local version**: Read from the first available source:\n   - `.claude-plugin\u002Fplugin.json` → `version` field\n   - `marketplace.json` → `plugins[0].version` field\n   - `CHANGELOG.md` → most recent version header\n   - Git tags → most recent `v*` tag\n\n   **Version parsing:** Normalize by stripping an optional `v` prefix and\n   trimming whitespace. If a source is present but yields an empty,\n   non-semver, or malformed string (invalid JSON, missing field), skip it\n   with a warning and try the next source. Only fall back to `0.0.0`\n   after all four sources fail.\n\n**If network access fails** (degraded mode):\n- Report the failure with error details.\n- Provide manual update instructions:\n  > Visit https:\u002F\u002Fgithub.com\u002Fproduct-on-purpose\u002Fpm-skills\u002Freleases to\n  > download the latest release. Extract the archive and copy the\n  > `skills\u002F`, `commands\u002F`, `_workflows\u002F`, and other content directories\n  > to your local pm-skills installation.\n- Stop execution.\n\n### Step 2: Version Comparison\n\nCompare the local version against the latest release using semver.\n\n**If local version >= latest version:**\n- Report: \"Your pm-skills installation is up to date (v{local}).\"\n- Offer to generate a report-only anyway.\n- Stop execution.\n\n**If local version \u003C latest version:**\n- Show the version delta:\n  ```\n  Local version:  v{local}\n  Latest version: v{latest}\n  Update type:    {major | minor | patch}\n  ```\n- **Major version warning**: If the update is a major bump (e.g., v2.x\n  to v3.x), show a prominent warning:\n  > This is a major version update. It may include breaking changes to\n  > skill contracts. Review the release notes before proceeding.\n- Continue to Step 3.\n\n### Step 3: Preview\n\nShow the user what the update includes:\n\n1. **Version delta**: local version, latest version, update type.\n\n2. **Value summary**: Derive from CHANGELOG entries between the two\n   versions, GitHub release notes, and directory diffs (new skills\u002F,\n   new _workflows\u002F files):\n   - New skills and what they enable\n   - Updated skills and what improved\n   - New workflows and what they connect\n   - Other notable changes\n\n3. **File manifest**: List of files and folders that will be written,\n   grouped by directory with counts:\n   ```\n   Files to be written:\n     skills\u002F       31 files (2 new, 29 updated)\n     commands\u002F     38 files (2 new, 36 updated)\n     _workflows\u002F    9 files (1 new, 8 updated)\n     other          7 files\n     Total:        85 files\n   ```\n\n**If `--report-only`:** Generate the report using `references\u002FTEMPLATE.md`\nwith the banner \"Report only - update was not applied.\" Save to\n`_pm-skills\u002Fupdates\u002Fupdate-report_v{latest}_report-only_{YYYY-MM-DD_HHMMSS}.md`. Stop\nexecution.\n\n### Step 4: Confirmation\n\nPrompt the user for two decisions:\n\n1. **Update confirmation**:\n   \"These files will be overwritten. Proceed? [yes \u002F no]\"\n   - If major version bump: require typing \"yes\" explicitly.\n   - If the user declines: save a report-only and stop.\n\n2. **Backup offer**:\n   \"Create a backup of current files before updating?\n   [yes (recommended) \u002F no]\"\n   - If yes: copy all in-scope files to\n     `_pm-skills\u002Fbackups\u002Fv{current}_{YYYY-MM-DD_HHMMSS}\u002F`\n   - Create the `_pm-skills\u002F` directory if it doesn't exist.\n\n### Step 5: Update\n\nExecute the update using validated-before-copy with backup:\n\n1. **Download**: Fetch the release ZIP asset (`pm-skills-vX.Y.Z.zip`)\n   from the GitHub Release page to a temporary directory. This is the\n   curated build artifact produced by `build-release.sh` - it includes\n   only user-facing content and excludes `docs\u002Finternal\u002F`.\n\n2. **Validate**: Confirm the extracted archive contains `skills\u002F`,\n   `commands\u002F`, `AGENTS.md`, and `.claude-plugin\u002Fplugin.json`. If\n   validation fails, report the error and stop without writing any files.\n\n3. **Copy**: Overwrite in-scope files from the extracted archive to the\n   install root. Show progress per directory:\n   ```\n   Updating pm-skills v2.9.0 -> v2.10.0...\n     skills\u002F       31\u002F31 ████████████████████  done\n     commands\u002F     38\u002F38 ████████████████████  done\n     _workflows\u002F    9\u002F9  ████████████████████  done\n     other files    7\u002F7  ████████████████████  done\n   ```\n\n4. **Clean up**: Remove the temporary directory.\n\n### Step 6: Post-Update\n\n1. **Smoke test**:\n   - Version consistency: `plugin.json`, `marketplace.json`, and\n     `CHANGELOG.md` all reflect the new version. (Note: version detection\n     in Step 1 uses first-match; the smoke test verifies all sources\n     agree. A mismatch here suggests a release packaging issue.)\n   - File integrity: `AGENTS.md`, `skills\u002F`, `commands\u002F`, `_workflows\u002F`\n     all exist.\n   - Skill count delta: count skills before and after, report the change.\n   - If any check fails: warn the user with specific details. Do NOT\n     auto-rollback. Provide recovery guidance:\n     - **Version mismatch**: \"Run the update again, or manually edit\n       {file} to set the version to {expected}.\"\n     - **Missing files**: \"Re-run `utility-update-pm-skills` to re-download,\n       or restore from backup: `cp -r _pm-skills\u002Fbackups\u002F{dir}\u002F* .`\"\n     - **If backup exists**: Always remind the user of the backup\n       location and restore command.\n\n2. **Summary line**: Show a single scannable confirmation:\n   ```\n   Updated v{old} -> v{new} | +{n} skills, +{n} workflows | Report: _pm-skills\u002Fupdates\u002F{file}\n   ```\n\n3. **Completion report**: Generate using `references\u002FTEMPLATE.md` and\n   save to `_pm-skills\u002Fupdates\u002Fupdate-report_v{from}-to-v{to}_{YYYY-MM-DD_HHMMSS}.md`\n\n4. **MCP advisory**: If `..\u002Fpm-skills-mcp\u002F` exists, try to read\n   `pm-skills-source.json`. If the file is missing or malformed, show:\n   \"pm-skills-mcp detected but pm-skills-source.json not found or\n   unreadable. Check the MCP repo manually.\" If readable, show:\n   ```\n   pm-skills-mcp detected at ..\u002Fpm-skills-mcp\u002F\n     Embedded skills version: v{embedded}\n     Updated pm-skills version: v{new}\n\n     To update the MCP server's embedded skills:\n       cd ..\u002Fpm-skills-mcp && npm run embed-skills && npm run build\n   ```\n\n5. **Next steps**:\n   ```\n   Next Steps:\n   - Review the update report at _pm-skills\u002Fupdates\u002F{report-file}\n   - Run utility-pm-skill-validate --all to verify skill integrity\n   - Run local CI: bash scripts\u002Flint-skills-frontmatter.sh\n   - Check release notes: {release-url}\n   ```\n\n## File Scope\n\nThe updater writes only files present in the release ZIP asset\n(`pm-skills-vX.Y.Z.zip`), which is the curated build produced by\n`build-release.sh`. As of v2.30.0 the ZIP also carries the `agents\u002F`\nsub-agent definitions and the `hooks\u002F` activation hooks, so a ZIP install\nhas the runtime files the dispatch skills reference. The ZIP excludes\n`docs\u002Finternal\u002F` and other non-user-facing content - no exclusion logic is\nneeded at copy time.\n\n**Files included in the release ZIP (updated):**\n\n| Path | Rationale |\n|------|-----------|\n| `skills\u002F` | Core skill files |\n| `commands\u002F` | Slash command definitions |\n| `_workflows\u002F` | Workflow chains |\n| `agents\u002F` | Sub-agent definitions the `utility-pm-*` dispatch skills read at runtime |\n| `hooks\u002F` | Activation hooks (guardrails + phase router) including `hooks.json` |\n| `library\u002F` | Sample library and skill output samples (note: user-added samples may be overwritten) |\n| `AGENTS.md` | Skill discovery for IDEs |\n| `.claude-plugin\u002Fplugin.json` | Version + plugin metadata |\n| `marketplace.json` | Marketplace metadata |\n| `CHANGELOG.md` | Release history |\n| `README.md` | Public docs |\n| `docs\u002F` (public guides, reference, workflows) | User-facing documentation |\n| `scripts\u002F` | CI\u002Fvalidation scripts |\n| `mkdocs.yml` | Docs site config |\n\n**Files NOT in the release ZIP (never overwritten):**\n\n| Path | Rationale |\n|------|-----------|\n| `docs\u002Finternal\u002F` | Excluded from ZIP by `build-release.sh` |\n| `_NOTES\u002F` | Local-only, gitignored, not in ZIP |\n| `_pm-skills\u002F` | Local state (reports, backups), not in ZIP |\n| `.github\u002F` | CI workflows, not in ZIP |\n| `CONTRIBUTING.md`, `LICENSE` | Not in ZIP (repo-level files) |\n\n## Output Contract\n\nThe skill MUST:\n- Validate network access before any remote operations\n- Show a preview before writing any files\n- Require explicit user confirmation before overwriting\n- Offer a backup before overwriting\n- Use validated-before-copy (download to temp, validate, then copy; backup is the recovery path for mid-copy failures)\n- Generate a report in both modes (report-only and completion)\n- Run the post-update smoke test\n- Show MCP advisory if sibling repo is detected\n\nThe skill MUST NOT:\n- Write files without user confirmation\n- Proceed without network access confirmation\n- Modify files outside the pm-skills directory\n- Modify `docs\u002Finternal\u002F`, `_NOTES\u002F`, or `_pm-skills\u002F` with upstream content\n- Auto-rollback on smoke test failure (inform the user instead)\n- Delete local files that don't exist in the upstream release\n\n## Quality Checklist\n\nBefore marking the update complete, verify:\n\n- [ ] Pre-flight passed: network, versions detected\n- [ ] User was shown preview before any files were written\n- [ ] User explicitly confirmed before update proceeded\n- [ ] Backup was offered (and created if accepted)\n- [ ] Archive was downloaded to temp and validated before copying\n- [ ] All in-scope files were written successfully\n- [ ] Version consistency: plugin.json, marketplace.json, CHANGELOG match\n- [ ] File integrity: AGENTS.md, skills\u002F, commands\u002F, _workflows\u002F exist\n- [ ] Skill count delta is reported (before -> after)\n- [ ] Report was generated and saved to `_pm-skills\u002Fupdates\u002F`\n- [ ] MCP advisory was shown if sibling repo detected\n- [ ] Next steps were presented\n- [ ] Summary line displayed\n\n## FAQ\n\n**I'm a contributor who cloned the repo. Should I use this skill?**\nNo. Use `git pull` or `git fetch && git merge` instead. This skill is\nfor end users who installed pm-skills as a plugin or downloaded a release.\n\n**Can I update to a specific version instead of the latest?**\nNot in v1. This skill always targets the latest release. To install a\nspecific version, download it manually from the releases page.\n\n**What happens to my local notes and planning docs?**\nThey are never touched. The skill explicitly excludes `docs\u002Finternal\u002F`,\n`_NOTES\u002F`, and `_pm-skills\u002F` from updates. See the File Scope table.\n\n**What happens to files I added that aren't in the upstream release?**\nThey are left untouched. The skill only overwrites files that exist in\nthe new release - it never deletes local files.\n\n**How do I undo an update?**\nIf you created a backup (the default offer), restore it:\n`cp -r _pm-skills\u002Fbackups\u002Fv{version}_{timestamp}\u002F* .`\nIf you didn't create a backup but have git, use `git checkout .` to\nrestore tracked files to their last committed state.\n\n**The update failed partway through. What do I do?**\nThe skill validates before copying (download to temp, check, then write),\nso partial failures are rare. If it does happen: restore from backup if\navailable, or re-run `utility-update-pm-skills` to retry.\n\n## Further Reading\n\nFor a visual walkthrough and additional context, see the\n[Updating PM Skills Guide](..\u002F..\u002Fsite\u002Fsrc\u002Fcontent\u002Fdocs\u002Fguides\u002Fupdating-pm-skills.md).\n",{"name":5,"license":15,"metadata":24,"description":7},{"author":9,"updated":25,"version":26,"category":27,"frameworks":28,"classification":30},1783123200000,"1.0.1","coordination",[29],"triple-diamond","utility","main","9b920db418c5bf641edea9afb4915a286e1d42ea","skills\u002Futility-update-pm-skills",102,"https:\u002F\u002Fgithub.com\u002Fproduct-on-purpose\u002Fpm-skills","https:\u002F\u002Fproduct-on-purpose.github.io\u002Fpm-skills\u002F","https:\u002F\u002Fgithub.com\u002Fproduct-on-purpose","2026-11-14 16:57:35",{"source":8,"skillName":5,"commands":40,"prompt":50,"zipAvailable":51},[41,44,47],{"tool":42,"command":43},"npx","npx skills add product-on-purpose\u002Fpm-skills --skill utility-update-pm-skills",{"tool":45,"command":46},"bunx","bunx skills add product-on-purpose\u002Fpm-skills --skill utility-update-pm-skills",{"tool":48,"command":49},"pnpm","pnpm dlx skills add product-on-purpose\u002Fpm-skills --skill utility-update-pm-skills","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fproduct-on-purpose\u002Fpm-skills\u002Fblob\u002Fmain\u002Fskills\u002Futility-update-pm-skills\u002FSKILL.md",true,[53,59,63,67],{"path":54,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":57,"sourceHtmlUrl":58},"evals\u002Ftrigger-fixtures.json","REFERENCE","参考文档",4861,"https:\u002F\u002Fgithub.com\u002Fproduct-on-purpose\u002Fpm-skills\u002Fblob\u002Fmain\u002Fskills\u002Futility-update-pm-skills\u002Fevals\u002Ftrigger-fixtures.json",{"path":60,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":61,"sourceHtmlUrl":62},"HISTORY.md",1580,"https:\u002F\u002Fgithub.com\u002Fproduct-on-purpose\u002Fpm-skills\u002Fblob\u002Fmain\u002Fskills\u002Futility-update-pm-skills\u002FHISTORY.md",{"path":64,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":65,"sourceHtmlUrl":66},"references\u002FEXAMPLE.md",5610,"https:\u002F\u002Fgithub.com\u002Fproduct-on-purpose\u002Fpm-skills\u002Fblob\u002Fmain\u002Fskills\u002Futility-update-pm-skills\u002Freferences\u002FEXAMPLE.md",{"path":68,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":69,"sourceHtmlUrl":70},"references\u002FTEMPLATE.md",4553,"https:\u002F\u002Fgithub.com\u002Fproduct-on-purpose\u002Fpm-skills\u002Fblob\u002Fmain\u002Fskills\u002Futility-update-pm-skills\u002Freferences\u002FTEMPLATE.md",[72,79,86,93,100,107],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M727QQSXYBZK7D29C80WMQ8M","utility-slideshow-creator","Generates professional presentations from a JSON deck specification using 18 slide types with dark\u002Flight variants, content-to-layout decision logic, and calibrated character limits. Ships with a default professional theme.","https:\u002F\u002Fgithub.com\u002Fproduct-on-purpose\u002Fpm-skills\u002Fblob\u002Fmain\u002Fskills\u002Futility-slideshow-creator\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M727QKYD45K0PCJ591046TK2","utility-pm-workflow-orchestrator","Run an ordered sequence of pm-skills against one input, pausing for go\u002Fno-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.","https:\u002F\u002Fgithub.com\u002Fproduct-on-purpose\u002Fpm-skills\u002Fblob\u002Fmain\u002Fskills\u002Futility-pm-workflow-orchestrator\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M727QFN6W9M8JGVXNQMT5642","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.","https:\u002F\u002Fgithub.com\u002Fproduct-on-purpose\u002Fpm-skills\u002Fblob\u002Fmain\u002Fskills\u002Futility-pm-workflow-builder\u002FSKILL.md",[],[],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":19},"01M727QCDS2WFTJPHXASSE5W6X","utility-pm-skill-validate","Audits an existing pm-skills skill against structural conventions and quality criteria. Produces a structured validation report with pass\u002Ffail checks, severity-graded findings, and actionable recommendations. Use when checking whether a skill meets repo standards before shipping or after making changes.","https:\u002F\u002Fgithub.com\u002Fproduct-on-purpose\u002Fpm-skills\u002Fblob\u002Fmain\u002Fskills\u002Futility-pm-skill-validate\u002FSKILL.md",[],[],{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":19},"01M727Q8GW1AZWPNWXYH7WHG9F","utility-pm-skill-iterate","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. Use when improving a skill after validation or feedback.","https:\u002F\u002Fgithub.com\u002Fproduct-on-purpose\u002Fpm-skills\u002Fblob\u002Fmain\u002Fskills\u002Futility-pm-skill-iterate\u002FSKILL.md",[],[],{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":113,"publishedAt":19},"01M727Q49TZERFYHQJTT8DCRK0","utility-pm-skill-builder","Guides contributors from a PM skill idea to a complete Skill Implementation Packet aligned with pm-skills conventions. Runs gap analysis, validates through a Why Gate, classifies by type and phase, generates draft files, and writes to a staging area for review before promotion.","https:\u002F\u002Fgithub.com\u002Fproduct-on-purpose\u002Fpm-skills\u002Fblob\u002Fmain\u002Fskills\u002Futility-pm-skill-builder\u002FSKILL.md",[],[]]