[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M727PB96571PXHG4G08BTF39":3,"skill-same:01M727PB96571PXHG4G08BTF39":87},{"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":51,"commitSha":52,"skillDirectory":53,"forksCount":54,"repositoryHtmlUrl":55,"repositoryHomepageUrl":56,"ownerHtmlUrl":57,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":58,"install":59,"resources":72},"01M727PB96571PXHG4G08BTF39","tool-foundation-sprint-readiness",null,"Pre-sprint diagnostic that determines whether a team should run a Foundation Sprint now, postpone it, or do prerequisite work first. Produces a Go \u002F Conditional Go \u002F Wait verdict with diagnosis, recommended preconditions, attendee list, and pre-sprint activities. Use when a team is considering starting a Foundation Sprint and wants a fast yes\u002Fno diagnosis before committing two days of facilitated work.","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\u002Ftool-foundation-sprint-readiness\u002FSKILL.md",[],[],"2026-11-10 18:39:20",false,"---\nname: tool-foundation-sprint-readiness\ndescription: Pre-sprint diagnostic that determines whether a team should run a Foundation Sprint now, postpone it, or do prerequisite work first. Produces a Go \u002F Conditional Go \u002F Wait verdict with diagnosis, recommended preconditions, attendee list, and pre-sprint activities. Use when a team is considering starting a Foundation Sprint and wants a fast yes\u002Fno diagnosis before committing two days of facilitated work.\nlicense: Apache-2.0\nmetadata:\n  classification: tool\n  version: \"1.0.0\"\n  updated: 2026-07-04\n  tool: foundation-sprint\n  move: readiness\n  category: coordination\n  frameworks:\n    - foundation-sprint\n    - click\n    - character-note-and-vote\n  timebox_minutes: 45\n  roles:\n    - facilitator\n    - pm\n    - decider\n  prerequisites: []\n  inputs:\n    - initiative description\n    - team composition draft\n    - decider name and availability\n    - existing customer or market knowledge level\n  outputs:\n    - readiness verdict\n    - diagnosis\n    - recommended preconditions\n    - recommended attendee list\n    - pre-sprint activities\n  author: product-on-purpose\n---\n\n\u003C!-- PM-Skills | https:\u002F\u002Fgithub.com\u002Fproduct-on-purpose\u002Fpm-skills | Apache 2.0 -->\n\n# Foundation Sprint Readiness\n\nAssess whether a Foundation Sprint fits the team's current situation. Most sprints that fail were sprints that should not have been run. A 30-45 minute readiness diagnostic catches that failure mode before two days of facilitated work are spent.\n\nFamily contract: [`site\u002Fsrc\u002Fcontent\u002Fdocs\u002Freference\u002Fskill-families\u002Ffoundation-sprint-skills-contract.md`](..\u002F..\u002Fsite\u002Fsrc\u002Fcontent\u002Fdocs\u002Freference\u002Fskill-families\u002Ffoundation-sprint-skills-contract.md). This skill is a member of `foundation-sprint-skills` and conforms to the family frontmatter and Decider Checkpoint requirements.\n\n## When to Use\n\n- A team is considering starting a Foundation Sprint and needs a fast diagnosis before committing two days.\n- A founder or PM has a \"should we run a Foundation Sprint?\" question and wants structured input rather than a vibes check.\n- An existing sprint commitment is on the calendar and the team wants to validate that prerequisites are in place.\n- Re-running a Foundation Sprint after invalidated assumptions: use to confirm new context is ready.\n\n## When NOT to Use\n\n- The team has already decided to run the sprint and just needs the brief. Use `tool-foundation-sprint-brief` instead.\n- The team needs deep customer discovery: run customer research or problem framing first; the Foundation Sprint depends on existing customer knowledge.\n- The decision is small and a full Foundation Sprint is overkill. Use a lighter prioritization or decision tool.\n- No Decider is available and one cannot be appointed. Foundation Sprint requires fast strategic calls; without authority it produces options without commitment.\n\n## What This Skill Produces\n\nA single bundled artifact with five sections:\n\n1. **Readiness verdict**: Go \u002F Conditional Go \u002F Wait\n2. **Diagnosis**: what is in place, what is missing, what is uncertain\n3. **Recommended preconditions** (when verdict is Wait or Conditional Go): the prerequisite work the team should do before the sprint\n4. **Recommended attendee list** (when verdict is Go or Conditional Go): the 3-5 people who should be in the room, with role expectations\n5. **Pre-sprint activities** (when verdict is Go): the prep work to complete in the days before Day 1\n\nSee `references\u002FTEMPLATE.md` for the canonical structure and `references\u002FEXAMPLE.md` for a worked example using the Brainshelf book-catalog thread.\n\n## Inference Inputs\n\nThe skill runs an inference pass over these inputs to produce the verdict:\n\n| Input | What the skill does with it |\n|---|---|\n| Initiative description | Determines whether a Foundation Sprint is the right tool (vs problem framing, customer research, or a Design Sprint) |\n| Team composition draft | Checks roster against the Foundation Sprint role requirements; flags missing roles |\n| Decider name and availability | Confirms Decider can attend both days; flags partial availability as Conditional Go risk |\n| Existing customer\u002Fmarket knowledge level (self-assessed 1-10) | Below 5 indicates deep discovery is needed first; 5-7 indicates Conditional Go with research prep; 8+ indicates Go |\n| (Optional) Existing competitor and alternative knowledge | Flags gaps that can be closed by overnight prep |\n| (Optional) Logistics constraints | Confirms two days can actually be cleared |\n\nIf a load-bearing input is missing or low-confidence, the skill flags it explicitly and proposes how to close the gap before the sprint.\n\n## Readiness Criteria (8 Canonical Checks)\n\nThe skill evaluates the team against these eight criteria, drawn from Knapp\u002FZeratsky (Click) and Character Capital's Foundation Sprint guide:\n\n1. **Initiative is named and concrete.** The team can name the project, product area, or strategic question.\n2. **The stakes are meaningful.** A wrong starting direction would be costly.\n3. **The team has existing knowledge.** Real customer, market, competitor, or domain context to make informed choices.\n4. **The Decider is available.** Strategic calls can be made during the sprint.\n5. **The team is small enough.** No more than five core decision participants is preferred.\n6. **Inputs are collected.** Existing research, customer examples, competitor notes, metrics are ready.\n7. **The output has a path to testing.** The team can use a Design Sprint, experiment, customer research, or another validation method afterward.\n8. **The organization tolerates explicit tradeoffs.** Foundation Sprint forces choosing a top bet and a backup, not preserving every possibility.\n\n| Pattern | Verdict |\n|---|---|\n| All 8 criteria met cleanly | **Go** |\n| 1-2 criteria are \"yellow flags\" but addressable in evening prep | **Conditional Go** with documented prep |\n| 3 or more criteria fail, or any of 1-4 is a hard fail | **Wait** with recommended prerequisite work |\n\nTreat the criteria as load-bearing, not a checklist to game. A team that papers over a real gap with \"yes, technically\" should get a Conditional Go with the gap surfaced.\n\n## Common Pitfalls\n\n- **Skipping the diagnostic because \"we're going to run it anyway.\"** This is the most common cause of failed sprints. The diagnostic costs 45 minutes; the failed sprint costs 16 hours of team time plus opportunity cost.\n- **Treating Conditional Go as Go without doing the prep.** Conditional Go means \"Go after closing these gaps.\" If the gaps are not closed by Day 1 morning, the sprint enters the failure mode the diagnostic was meant to prevent.\n- **Confusing readiness assessment with problem framing.** This skill assesses whether to run a Foundation Sprint, not whether the team has the right problem. If the problem is unclear, the verdict is Wait with \"do problem framing first\" as the precondition.\n- **No Decider, no sprint.** A team with no Decider available is not ready, full stop. Appointing a \"Decider for the day\" who lacks real authority does not solve this.\n- **Cargo-cult readiness.** Reading the criteria and answering yes to all eight without checking does not produce readiness. The skill's value is in the honest diagnosis.\n\n## Canonical Sources\n\n- Knapp, J., and Zeratsky, J. *Click: How to Make What People Want*. Foundation Sprint readiness guidance.\n- Character Capital. \"Foundation Sprint guide.\" https:\u002F\u002Fwww.character.vc\u002Fguide\u002Ffoundation-sprint\n- Design Sprint Academy. \"Foundation Sprint readiness criteria for enterprise.\" Used for the enterprise-context adjustments to canonical readiness.\n\n## Cross-Skill Usage\n\nThis skill is the entry point of the foundation-sprint-skills family. It has no prerequisites (the `metadata.prerequisites` field is intentionally empty).\n\nWhen the verdict is Go, the natural next invocation is `tool-foundation-sprint-brief` to set up the sprint logistics. When the verdict is Wait, the team typically does prerequisite work (problem framing, customer research) before re-invoking this skill.\n\n`tool-note-and-vote` may be invoked once during the readiness conversation if the team disagrees on whether a Foundation Sprint is the right tool. In practice, this is rare; the diagnostic is usually conclusive.\n\n## Decider Checkpoint\n\nThis skill ends with a Decider Checkpoint in `references\u002FTEMPLATE.md`. The Decider signs off on the verdict (Go \u002F Conditional Go \u002F Wait) and explicitly accepts the diagnosis. Without Decider sign-off, the verdict is advisory; with sign-off, it is the commitment that triggers (or postpones) the sprint.\n","\u003C!-- PM-Skills | https:\u002F\u002Fgithub.com\u002Fproduct-on-purpose\u002Fpm-skills | Apache 2.0 -->\n\n# Foundation Sprint Readiness\n\nAssess whether a Foundation Sprint fits the team's current situation. Most sprints that fail were sprints that should not have been run. A 30-45 minute readiness diagnostic catches that failure mode before two days of facilitated work are spent.\n\nFamily contract: [`site\u002Fsrc\u002Fcontent\u002Fdocs\u002Freference\u002Fskill-families\u002Ffoundation-sprint-skills-contract.md`](..\u002F..\u002Fsite\u002Fsrc\u002Fcontent\u002Fdocs\u002Freference\u002Fskill-families\u002Ffoundation-sprint-skills-contract.md). This skill is a member of `foundation-sprint-skills` and conforms to the family frontmatter and Decider Checkpoint requirements.\n\n## When to Use\n\n- A team is considering starting a Foundation Sprint and needs a fast diagnosis before committing two days.\n- A founder or PM has a \"should we run a Foundation Sprint?\" question and wants structured input rather than a vibes check.\n- An existing sprint commitment is on the calendar and the team wants to validate that prerequisites are in place.\n- Re-running a Foundation Sprint after invalidated assumptions: use to confirm new context is ready.\n\n## When NOT to Use\n\n- The team has already decided to run the sprint and just needs the brief. Use `tool-foundation-sprint-brief` instead.\n- The team needs deep customer discovery: run customer research or problem framing first; the Foundation Sprint depends on existing customer knowledge.\n- The decision is small and a full Foundation Sprint is overkill. Use a lighter prioritization or decision tool.\n- No Decider is available and one cannot be appointed. Foundation Sprint requires fast strategic calls; without authority it produces options without commitment.\n\n## What This Skill Produces\n\nA single bundled artifact with five sections:\n\n1. **Readiness verdict**: Go \u002F Conditional Go \u002F Wait\n2. **Diagnosis**: what is in place, what is missing, what is uncertain\n3. **Recommended preconditions** (when verdict is Wait or Conditional Go): the prerequisite work the team should do before the sprint\n4. **Recommended attendee list** (when verdict is Go or Conditional Go): the 3-5 people who should be in the room, with role expectations\n5. **Pre-sprint activities** (when verdict is Go): the prep work to complete in the days before Day 1\n\nSee `references\u002FTEMPLATE.md` for the canonical structure and `references\u002FEXAMPLE.md` for a worked example using the Brainshelf book-catalog thread.\n\n## Inference Inputs\n\nThe skill runs an inference pass over these inputs to produce the verdict:\n\n| Input | What the skill does with it |\n|---|---|\n| Initiative description | Determines whether a Foundation Sprint is the right tool (vs problem framing, customer research, or a Design Sprint) |\n| Team composition draft | Checks roster against the Foundation Sprint role requirements; flags missing roles |\n| Decider name and availability | Confirms Decider can attend both days; flags partial availability as Conditional Go risk |\n| Existing customer\u002Fmarket knowledge level (self-assessed 1-10) | Below 5 indicates deep discovery is needed first; 5-7 indicates Conditional Go with research prep; 8+ indicates Go |\n| (Optional) Existing competitor and alternative knowledge | Flags gaps that can be closed by overnight prep |\n| (Optional) Logistics constraints | Confirms two days can actually be cleared |\n\nIf a load-bearing input is missing or low-confidence, the skill flags it explicitly and proposes how to close the gap before the sprint.\n\n## Readiness Criteria (8 Canonical Checks)\n\nThe skill evaluates the team against these eight criteria, drawn from Knapp\u002FZeratsky (Click) and Character Capital's Foundation Sprint guide:\n\n1. **Initiative is named and concrete.** The team can name the project, product area, or strategic question.\n2. **The stakes are meaningful.** A wrong starting direction would be costly.\n3. **The team has existing knowledge.** Real customer, market, competitor, or domain context to make informed choices.\n4. **The Decider is available.** Strategic calls can be made during the sprint.\n5. **The team is small enough.** No more than five core decision participants is preferred.\n6. **Inputs are collected.** Existing research, customer examples, competitor notes, metrics are ready.\n7. **The output has a path to testing.** The team can use a Design Sprint, experiment, customer research, or another validation method afterward.\n8. **The organization tolerates explicit tradeoffs.** Foundation Sprint forces choosing a top bet and a backup, not preserving every possibility.\n\n| Pattern | Verdict |\n|---|---|\n| All 8 criteria met cleanly | **Go** |\n| 1-2 criteria are \"yellow flags\" but addressable in evening prep | **Conditional Go** with documented prep |\n| 3 or more criteria fail, or any of 1-4 is a hard fail | **Wait** with recommended prerequisite work |\n\nTreat the criteria as load-bearing, not a checklist to game. A team that papers over a real gap with \"yes, technically\" should get a Conditional Go with the gap surfaced.\n\n## Common Pitfalls\n\n- **Skipping the diagnostic because \"we're going to run it anyway.\"** This is the most common cause of failed sprints. The diagnostic costs 45 minutes; the failed sprint costs 16 hours of team time plus opportunity cost.\n- **Treating Conditional Go as Go without doing the prep.** Conditional Go means \"Go after closing these gaps.\" If the gaps are not closed by Day 1 morning, the sprint enters the failure mode the diagnostic was meant to prevent.\n- **Confusing readiness assessment with problem framing.** This skill assesses whether to run a Foundation Sprint, not whether the team has the right problem. If the problem is unclear, the verdict is Wait with \"do problem framing first\" as the precondition.\n- **No Decider, no sprint.** A team with no Decider available is not ready, full stop. Appointing a \"Decider for the day\" who lacks real authority does not solve this.\n- **Cargo-cult readiness.** Reading the criteria and answering yes to all eight without checking does not produce readiness. The skill's value is in the honest diagnosis.\n\n## Canonical Sources\n\n- Knapp, J., and Zeratsky, J. *Click: How to Make What People Want*. Foundation Sprint readiness guidance.\n- Character Capital. \"Foundation Sprint guide.\" https:\u002F\u002Fwww.character.vc\u002Fguide\u002Ffoundation-sprint\n- Design Sprint Academy. \"Foundation Sprint readiness criteria for enterprise.\" Used for the enterprise-context adjustments to canonical readiness.\n\n## Cross-Skill Usage\n\nThis skill is the entry point of the foundation-sprint-skills family. It has no prerequisites (the `metadata.prerequisites` field is intentionally empty).\n\nWhen the verdict is Go, the natural next invocation is `tool-foundation-sprint-brief` to set up the sprint logistics. When the verdict is Wait, the team typically does prerequisite work (problem framing, customer research) before re-invoking this skill.\n\n`tool-note-and-vote` may be invoked once during the readiness conversation if the team disagrees on whether a Foundation Sprint is the right tool. In practice, this is rare; the diagnostic is usually conclusive.\n\n## Decider Checkpoint\n\nThis skill ends with a Decider Checkpoint in `references\u002FTEMPLATE.md`. The Decider signs off on the verdict (Go \u002F Conditional Go \u002F Wait) and explicitly accepts the diagnosis. Without Decider sign-off, the verdict is advisory; with sign-off, it is the commitment that triggers (or postpones) the sprint.\n",{"name":5,"license":15,"metadata":24,"description":7},{"move":25,"tool":26,"roles":27,"author":9,"inputs":31,"outputs":36,"updated":42,"version":43,"category":44,"frameworks":45,"prerequisites":48,"classification":49,"timebox_minutes":50},"readiness","foundation-sprint",[28,29,30],"facilitator","pm","decider",[32,33,34,35],"initiative description","team composition draft","decider name and availability","existing customer or market knowledge level",[37,38,39,40,41],"readiness verdict","diagnosis","recommended preconditions","recommended attendee list","pre-sprint activities",1783123200000,"1.0.0","coordination",[26,46,47],"click","character-note-and-vote",[],"tool",45,"main","9b920db418c5bf641edea9afb4915a286e1d42ea","skills\u002Ftool-foundation-sprint-readiness",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":60,"prompt":70,"zipAvailable":71},[61,64,67],{"tool":62,"command":63},"npx","npx skills add product-on-purpose\u002Fpm-skills --skill tool-foundation-sprint-readiness",{"tool":65,"command":66},"bunx","bunx skills add product-on-purpose\u002Fpm-skills --skill tool-foundation-sprint-readiness",{"tool":68,"command":69},"pnpm","pnpm dlx skills add product-on-purpose\u002Fpm-skills --skill tool-foundation-sprint-readiness","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fproduct-on-purpose\u002Fpm-skills\u002Fblob\u002Fmain\u002Fskills\u002Ftool-foundation-sprint-readiness\u002FSKILL.md",true,[73,79,83],{"path":74,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":77,"sourceHtmlUrl":78},"HISTORY.md","REFERENCE","参考文档",821,"https:\u002F\u002Fgithub.com\u002Fproduct-on-purpose\u002Fpm-skills\u002Fblob\u002Fmain\u002Fskills\u002Ftool-foundation-sprint-readiness\u002FHISTORY.md",{"path":80,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":81,"sourceHtmlUrl":82},"references\u002FEXAMPLE.md",5987,"https:\u002F\u002Fgithub.com\u002Fproduct-on-purpose\u002Fpm-skills\u002Fblob\u002Fmain\u002Fskills\u002Ftool-foundation-sprint-readiness\u002Freferences\u002FEXAMPLE.md",{"path":84,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":85,"sourceHtmlUrl":86},"references\u002FTEMPLATE.md",3877,"https:\u002F\u002Fgithub.com\u002Fproduct-on-purpose\u002Fpm-skills\u002Fblob\u002Fmain\u002Fskills\u002Ftool-foundation-sprint-readiness\u002Freferences\u002FTEMPLATE.md",[88,95,102,109,116,123],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"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":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"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":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":108,"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":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":115,"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":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":120,"categories":121,"keywords":122,"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":124,"name":125,"nameZh":6,"description":126,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":127,"categories":128,"keywords":129,"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",[],[]]