[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M727K5D0H8PRSB3A77T5JEQY":3,"skill-same:01M727K5D0H8PRSB3A77T5JEQY":79},{"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},"01M727K5D0H8PRSB3A77T5JEQY","foundation-stakeholder-briefings",null,"Turns any source artifact (spec, discovery, research, GTM plan, experiment results, retro, or raw notes) into one canonical master document plus a set of audience-tailored briefings, each re-pitched to a stakeholder lens (executive, board, engineering, UX, PMM, sales, CS, legal, data, or a custom audience). Every briefing is a traceable projection of the master, so the versions never disagree. Use when one piece of work must reach several audiences who each need a different framing, decision, and level of detail.","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\u002Ffoundation-stakeholder-briefings\u002FSKILL.md",[],[],"2026-11-10 18:39:20",false,"---\nname: foundation-stakeholder-briefings\ndescription: \"Turns any source artifact (spec, discovery, research, GTM plan, experiment results, retro, or raw notes) into one canonical master document plus a set of audience-tailored briefings, each re-pitched to a stakeholder lens (executive, board, engineering, UX, PMM, sales, CS, legal, data, or a custom audience). Every briefing is a traceable projection of the master, so the versions never disagree. Use when one piece of work must reach several audiences who each need a different framing, decision, and level of detail.\"\nlicense: Apache-2.0\nmetadata:\n  classification: foundation\n  version: \"1.0.1\"\n  updated: 2026-07-04\n  category: communication\n  frameworks: [stakeholder-comms]\n  author: product-on-purpose\n---\n\u003C!-- PM-Skills | https:\u002F\u002Fgithub.com\u002Fproduct-on-purpose\u002Fpm-skills | Apache 2.0 -->\n# Stakeholder Briefings\n\nA stakeholder-briefings artifact takes one source (a PRD, a discovery synthesis, a research report, a GTM or launch plan, experiment results, a retro or incident write-up, or raw notes) and produces a single saveable file containing:\n\n1. a **master document**: the canonical, audience-neutral synthesis of the work (what and why, decisions, status, risks and open questions, asks, timeline), with each claim numbered (`M1`, `M2`, ...); and\n2. a set of **audience briefings**: the same content re-pitched for each chosen stakeholder, one self-contained, copy-paste-ready block per audience.\n\nThe skill runs **master-first, then projects**. The master is the single source of truth; every briefing is a projection of it. A briefing may omit, reorder, and translate master content, but it may never assert a claim that is not in the master. That projection rule is what keeps the executive version and the engineering version from quietly disagreeing, and it is the difference between this skill and asking a model to \"rewrite this six ways.\"\n\nDistinct from `foundation-stakeholder-update` (one async update of meeting outcomes for a single audience, meeting-bound), `discover-stakeholder-summary` (a map of who stakeholders are and their influence\u002Finterest), and `foundation-persona` (a customer\u002Fbuyer viewpoint to design or market against).\n\n## When to Use\n\n- One piece of work must reach several audiences who each need a different framing, decision, and level of detail (a spec going to engineering, design, data, and the funder at once).\n- You are about to manually rewrite the same update three to five ways, one per audience.\n- A decision or result needs to propagate across functions without the versions drifting apart.\n- A single audience needs a tailored briefing from a non-meeting source (N=1 is supported; the fan-out is the signature use, not a floor).\n\n## When NOT to Use\n\n- One async update of **meeting** outcomes for stakeholders. Use `foundation-stakeholder-update` (it is meeting-bound; that is its scope).\n- Understanding or mapping stakeholders (influence, interest, comms plan). Use `discover-stakeholder-summary`.\n- A persona to design or market against. Use `foundation-persona`.\n- There is no source content yet. This skill projects an existing artifact; it does not do the underlying analysis.\n\n## Instructions\n\nWhen asked to create stakeholder briefings, follow these steps:\n\n1. **Ingest and classify the source.** Read the provided artifact. Classify its type (spec\u002FPRD, discovery\u002Fresearch, GTM\u002Flaunch, strategy\u002Froadmap, experiment\u002Fmetrics, incident\u002Fretro, compliance\u002Fprivacy\u002Fsecurity, or raw\u002Fambiguous). If the source is thin, continue but set `input_quality: low` and name the gap.\n\n2. **Build the master.** Write the audience-neutral canonical document with these sections: What and Why, Decisions, Status, Risks and Open Questions, Asks, Timeline. **Number every load-bearing claim** with a stable ID (`M1`, `M2`, ...). The master carries no audience-specific spin; it is the shared substrate.\n\n3. **Propose the audiences.** From the source type, propose the relevant subset using `references\u002Fsource-type-map.md` (for example, a spec proposes Engineering, UX\u002FDesign, Data\u002FBI, Executive; a GTM plan proposes PMM, Sales, CS\u002FSupport, Executive). Present the proposal and accept `go` (generate the proposed set), an edit (`drop X, add Y`), or `all` (all nine). If invoked with `--go`, skip the prompt and generate the proposal. No audience is ever locked out.\n\n4. **Project each briefing.** For each chosen lens (see `references\u002Faudience-lenses.md`), render a self-contained block delimited by `--- BEGIN: \u003Clens> ---` \u002F `--- END ---`, containing:\n   - `Draws on:` the master claim IDs this briefing projects (required).\n   - `Primary ask:` exactly one decision or action for this audience (required).\n   - a one-line headline, a \"what this means for you\" framing, and the body, at the lens's length, vocabulary, and tone.\n   Every load-bearing line must trace to a master claim. Do not introduce a claim that is not in the master.\n\n5. **Flag translations.** Keep a translations-applied log (internal, below the shareable boundary) for every technical-to-business or inferred re-pitch, so the user can verify it lands. This section is never part of a shareable briefing.\n\n6. **Self-check the invariant** before finalizing:\n   - **Trace references resolve** (deterministic, checkable): every briefing `Draws on:` ID resolves to a real master claim.\n   - **One CTA** (deterministic, checkable): exactly one `Primary ask:` per block.\n   - **No untraced claim** (review): re-read each block against its `Draws on:` set and confirm the body introduces nothing absent from those master claims. This is a review step, not automated.\n   - **Neutral master** (review): the master has no audience-specific spin. List anything that fails.\n\n7. **Render the artifact.** Master (with claim IDs) -> the delimited briefing blocks -> the boundary marker -> the translations-applied log -> Sources and References. Remove all guidance blockquotes from the final output.\n\n## Audience lenses\n\nNine first-class lenses, each defined by the decision it owns, plus a Custom slot whose lens is inferred from the audience name and source and shown for confirmation. Full definitions, per-lens \"not this lens when\" boundaries, and the overlap matrix (Exec vs Board, PMM vs Sales, Engineering vs Data, Legal vs Exec) are in `references\u002Faudience-lenses.md`.\n\n## Output Format\n\n- A single artifact (filename `YYYY-MM-DD_HH-MMtz_\u003Ctitle>_stakeholder-briefings.md`), built from `references\u002FTEMPLATE.md`.\n- Each briefing block is self-contained and send-ready (BEGIN\u002FEND cut-lines) so it can be copied out without edits.\n- A future `--split` mode (write each block to its own file) is deferred; v1 is single-artifact.\n\n## Quality Checklist\n\n- [ ] Master present with numbered claim IDs (`M1`, `M2`, ...) and no audience-specific spin.\n- [ ] Each briefing block has a `Draws on:` line whose IDs all resolve to master claims.\n- [ ] Each briefing block has exactly one `Primary ask:`.\n- [ ] No briefing asserts a claim absent from the master (projection rule).\n- [ ] Audience set matches the source-type proposal or the user's edit; N=1 honored without refusal.\n- [ ] Translations-applied log present (internal) when any translation was made; boundary marker separates shareable blocks from internal sections.\n- [ ] Each briefing is at the lens's length and tone (a board block reads nothing like an engineering block).\n- [ ] Guidance blockquotes removed from the final artifact.\n\n## See also\n\n- [`references\u002FTEMPLATE.md`](references\u002FTEMPLATE.md) - the master + briefing-block scaffold.\n- [`references\u002Faudience-lenses.md`](references\u002Faudience-lenses.md) - the nine lenses, boundaries, and overlap matrix.\n- [`references\u002Fsource-type-map.md`](references\u002Fsource-type-map.md) - the source-type to audience proposal.\n- [`foundation-stakeholder-update`](..\u002Ffoundation-stakeholder-update\u002FSKILL.md) - one meeting update for one audience (distinct).\n- [`discover-stakeholder-summary`](..\u002Fdiscover-stakeholder-summary\u002FSKILL.md) - mapping stakeholders (distinct).\n","\u003C!-- PM-Skills | https:\u002F\u002Fgithub.com\u002Fproduct-on-purpose\u002Fpm-skills | Apache 2.0 -->\n# Stakeholder Briefings\n\nA stakeholder-briefings artifact takes one source (a PRD, a discovery synthesis, a research report, a GTM or launch plan, experiment results, a retro or incident write-up, or raw notes) and produces a single saveable file containing:\n\n1. a **master document**: the canonical, audience-neutral synthesis of the work (what and why, decisions, status, risks and open questions, asks, timeline), with each claim numbered (`M1`, `M2`, ...); and\n2. a set of **audience briefings**: the same content re-pitched for each chosen stakeholder, one self-contained, copy-paste-ready block per audience.\n\nThe skill runs **master-first, then projects**. The master is the single source of truth; every briefing is a projection of it. A briefing may omit, reorder, and translate master content, but it may never assert a claim that is not in the master. That projection rule is what keeps the executive version and the engineering version from quietly disagreeing, and it is the difference between this skill and asking a model to \"rewrite this six ways.\"\n\nDistinct from `foundation-stakeholder-update` (one async update of meeting outcomes for a single audience, meeting-bound), `discover-stakeholder-summary` (a map of who stakeholders are and their influence\u002Finterest), and `foundation-persona` (a customer\u002Fbuyer viewpoint to design or market against).\n\n## When to Use\n\n- One piece of work must reach several audiences who each need a different framing, decision, and level of detail (a spec going to engineering, design, data, and the funder at once).\n- You are about to manually rewrite the same update three to five ways, one per audience.\n- A decision or result needs to propagate across functions without the versions drifting apart.\n- A single audience needs a tailored briefing from a non-meeting source (N=1 is supported; the fan-out is the signature use, not a floor).\n\n## When NOT to Use\n\n- One async update of **meeting** outcomes for stakeholders. Use `foundation-stakeholder-update` (it is meeting-bound; that is its scope).\n- Understanding or mapping stakeholders (influence, interest, comms plan). Use `discover-stakeholder-summary`.\n- A persona to design or market against. Use `foundation-persona`.\n- There is no source content yet. This skill projects an existing artifact; it does not do the underlying analysis.\n\n## Instructions\n\nWhen asked to create stakeholder briefings, follow these steps:\n\n1. **Ingest and classify the source.** Read the provided artifact. Classify its type (spec\u002FPRD, discovery\u002Fresearch, GTM\u002Flaunch, strategy\u002Froadmap, experiment\u002Fmetrics, incident\u002Fretro, compliance\u002Fprivacy\u002Fsecurity, or raw\u002Fambiguous). If the source is thin, continue but set `input_quality: low` and name the gap.\n\n2. **Build the master.** Write the audience-neutral canonical document with these sections: What and Why, Decisions, Status, Risks and Open Questions, Asks, Timeline. **Number every load-bearing claim** with a stable ID (`M1`, `M2`, ...). The master carries no audience-specific spin; it is the shared substrate.\n\n3. **Propose the audiences.** From the source type, propose the relevant subset using `references\u002Fsource-type-map.md` (for example, a spec proposes Engineering, UX\u002FDesign, Data\u002FBI, Executive; a GTM plan proposes PMM, Sales, CS\u002FSupport, Executive). Present the proposal and accept `go` (generate the proposed set), an edit (`drop X, add Y`), or `all` (all nine). If invoked with `--go`, skip the prompt and generate the proposal. No audience is ever locked out.\n\n4. **Project each briefing.** For each chosen lens (see `references\u002Faudience-lenses.md`), render a self-contained block delimited by `--- BEGIN: \u003Clens> ---` \u002F `--- END ---`, containing:\n   - `Draws on:` the master claim IDs this briefing projects (required).\n   - `Primary ask:` exactly one decision or action for this audience (required).\n   - a one-line headline, a \"what this means for you\" framing, and the body, at the lens's length, vocabulary, and tone.\n   Every load-bearing line must trace to a master claim. Do not introduce a claim that is not in the master.\n\n5. **Flag translations.** Keep a translations-applied log (internal, below the shareable boundary) for every technical-to-business or inferred re-pitch, so the user can verify it lands. This section is never part of a shareable briefing.\n\n6. **Self-check the invariant** before finalizing:\n   - **Trace references resolve** (deterministic, checkable): every briefing `Draws on:` ID resolves to a real master claim.\n   - **One CTA** (deterministic, checkable): exactly one `Primary ask:` per block.\n   - **No untraced claim** (review): re-read each block against its `Draws on:` set and confirm the body introduces nothing absent from those master claims. This is a review step, not automated.\n   - **Neutral master** (review): the master has no audience-specific spin. List anything that fails.\n\n7. **Render the artifact.** Master (with claim IDs) -> the delimited briefing blocks -> the boundary marker -> the translations-applied log -> Sources and References. Remove all guidance blockquotes from the final output.\n\n## Audience lenses\n\nNine first-class lenses, each defined by the decision it owns, plus a Custom slot whose lens is inferred from the audience name and source and shown for confirmation. Full definitions, per-lens \"not this lens when\" boundaries, and the overlap matrix (Exec vs Board, PMM vs Sales, Engineering vs Data, Legal vs Exec) are in `references\u002Faudience-lenses.md`.\n\n## Output Format\n\n- A single artifact (filename `YYYY-MM-DD_HH-MMtz_\u003Ctitle>_stakeholder-briefings.md`), built from `references\u002FTEMPLATE.md`.\n- Each briefing block is self-contained and send-ready (BEGIN\u002FEND cut-lines) so it can be copied out without edits.\n- A future `--split` mode (write each block to its own file) is deferred; v1 is single-artifact.\n\n## Quality Checklist\n\n- [ ] Master present with numbered claim IDs (`M1`, `M2`, ...) and no audience-specific spin.\n- [ ] Each briefing block has a `Draws on:` line whose IDs all resolve to master claims.\n- [ ] Each briefing block has exactly one `Primary ask:`.\n- [ ] No briefing asserts a claim absent from the master (projection rule).\n- [ ] Audience set matches the source-type proposal or the user's edit; N=1 honored without refusal.\n- [ ] Translations-applied log present (internal) when any translation was made; boundary marker separates shareable blocks from internal sections.\n- [ ] Each briefing is at the lens's length and tone (a board block reads nothing like an engineering block).\n- [ ] Guidance blockquotes removed from the final artifact.\n\n## See also\n\n- [`references\u002FTEMPLATE.md`](references\u002FTEMPLATE.md) - the master + briefing-block scaffold.\n- [`references\u002Faudience-lenses.md`](references\u002Faudience-lenses.md) - the nine lenses, boundaries, and overlap matrix.\n- [`references\u002Fsource-type-map.md`](references\u002Fsource-type-map.md) - the source-type to audience proposal.\n- [`foundation-stakeholder-update`](..\u002Ffoundation-stakeholder-update\u002FSKILL.md) - one meeting update for one audience (distinct).\n- [`discover-stakeholder-summary`](..\u002Fdiscover-stakeholder-summary\u002FSKILL.md) - mapping stakeholders (distinct).\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","communication",[29],"stakeholder-comms","foundation","main","9b920db418c5bf641edea9afb4915a286e1d42ea","skills\u002Ffoundation-stakeholder-briefings",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 foundation-stakeholder-briefings",{"tool":45,"command":46},"bunx","bunx skills add product-on-purpose\u002Fpm-skills --skill foundation-stakeholder-briefings",{"tool":48,"command":49},"pnpm","pnpm dlx skills add product-on-purpose\u002Fpm-skills --skill foundation-stakeholder-briefings","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fproduct-on-purpose\u002Fpm-skills\u002Fblob\u002Fmain\u002Fskills\u002Ffoundation-stakeholder-briefings\u002FSKILL.md",true,[53,59,63,67,71,75],{"path":54,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":57,"sourceHtmlUrl":58},"evals\u002Ftrigger-fixtures.json","REFERENCE","参考文档",4115,"https:\u002F\u002Fgithub.com\u002Fproduct-on-purpose\u002Fpm-skills\u002Fblob\u002Fmain\u002Fskills\u002Ffoundation-stakeholder-briefings\u002Fevals\u002Ftrigger-fixtures.json",{"path":60,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":61,"sourceHtmlUrl":62},"HISTORY.md",1756,"https:\u002F\u002Fgithub.com\u002Fproduct-on-purpose\u002Fpm-skills\u002Fblob\u002Fmain\u002Fskills\u002Ffoundation-stakeholder-briefings\u002FHISTORY.md",{"path":64,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":65,"sourceHtmlUrl":66},"references\u002Faudience-lenses.md",4799,"https:\u002F\u002Fgithub.com\u002Fproduct-on-purpose\u002Fpm-skills\u002Fblob\u002Fmain\u002Fskills\u002Ffoundation-stakeholder-briefings\u002Freferences\u002Faudience-lenses.md",{"path":68,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":69,"sourceHtmlUrl":70},"references\u002FEXAMPLE.md",5111,"https:\u002F\u002Fgithub.com\u002Fproduct-on-purpose\u002Fpm-skills\u002Fblob\u002Fmain\u002Fskills\u002Ffoundation-stakeholder-briefings\u002Freferences\u002FEXAMPLE.md",{"path":72,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":73,"sourceHtmlUrl":74},"references\u002Fsource-type-map.md",2612,"https:\u002F\u002Fgithub.com\u002Fproduct-on-purpose\u002Fpm-skills\u002Fblob\u002Fmain\u002Fskills\u002Ffoundation-stakeholder-briefings\u002Freferences\u002Fsource-type-map.md",{"path":76,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":77,"sourceHtmlUrl":78},"references\u002FTEMPLATE.md",2771,"https:\u002F\u002Fgithub.com\u002Fproduct-on-purpose\u002Fpm-skills\u002Fblob\u002Fmain\u002Fskills\u002Ffoundation-stakeholder-briefings\u002Freferences\u002FTEMPLATE.md",[80,87,94,101,108,115],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M727QTD4J5TPP3EEYPXMGZE4","utility-update-pm-skills","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.","https:\u002F\u002Fgithub.com\u002Fproduct-on-purpose\u002Fpm-skills\u002Fblob\u002Fmain\u002Fskills\u002Futility-update-pm-skills\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"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":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"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":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":107,"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":109,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":112,"categories":113,"keywords":114,"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":116,"name":117,"nameZh":6,"description":118,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":119,"categories":120,"keywords":121,"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",[],[]]