[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M727GKHPFRMSB5Y4TKSM6HZ9":3,"skill-same:01M727GKHPFRMSB5Y4TKSM6HZ9":73},{"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":33,"commitSha":34,"skillDirectory":35,"forksCount":36,"repositoryHtmlUrl":37,"repositoryHomepageUrl":38,"ownerHtmlUrl":39,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":40,"install":41,"resources":54},"01M727GKHPFRMSB5Y4TKSM6HZ9","deliver-launch-checklist",null,"Creates a cross-functional pre-launch checklist covering engineering, design, marketing, support, legal, and operations readiness, with owners, dates, and go\u002Fno-go criteria so nothing is missed before release. Use for significant or cross-team launches, not a small single-team change. For the customer-facing announcement of what shipped, use deliver-release-notes instead.","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\u002Fdeliver-launch-checklist\u002FSKILL.md",[],[],"2026-11-10 18:39:20",false,"---\nname: deliver-launch-checklist\ndescription: Creates a cross-functional pre-launch checklist covering engineering, design, marketing, support, legal, and operations readiness, with owners, dates, and go\u002Fno-go criteria so nothing is missed before release. Use for significant or cross-team launches, not a small single-team change. For the customer-facing announcement of what shipped, use deliver-release-notes instead.\nlicense: Apache-2.0\nmetadata:\n  phase: deliver\n  version: \"2.2.0\"\n  updated: 2026-07-04\n  category: coordination\n  frameworks: [triple-diamond, lean-startup, design-thinking]\n  author: product-on-purpose\n---\n\u003C!-- PM-Skills | https:\u002F\u002Fgithub.com\u002Fproduct-on-purpose\u002Fpm-skills | Apache 2.0 -->\n# Launch Checklist\n\nA launch checklist is a comprehensive verification document that ensures all functions are ready before releasing a feature or product. It coordinates across engineering, QA, design, marketing, support, legal, and operations to prevent launch-day surprises. Good launch checklists surface blockers early and create shared accountability for launch readiness.\n\n## When to Use\n\n- 1-2 weeks before any significant launch\n- During launch planning kickoff meetings\n- When coordinating cross-functional releases\n- Before major version releases or feature rollouts\n- After incidents to improve launch processes\n\n## When NOT to Use\n\n- You are validating whether to ship at all via an experiment -> use `measure-experiment-design`\n- You need the customer-facing announcement of what shipped -> use `deliver-release-notes`\n- The launch already happened and you want results or reflection -> use `measure-experiment-results` or `iterate-retrospective`\n- The change is small and single-team with no cross-functional surface: a launch checklist adds ceremony without value; track it in the sprint instead\n\n## Instructions\n\nWhen asked to create a launch checklist, follow these steps:\n\n1. **Define Launch Context**\n   Document what is launching, when, and who the key stakeholders are. Establish the launch tier (major release, minor feature, experiment) as this affects checklist scope.\n\n2. **Gather Functional Requirements**\n   For each function (engineering, QA, marketing, etc.), identify what must be complete, verified, or in place before launch. Distinguish between blockers (must-have) and nice-to-haves.\n\n3. **Assign Owners and Dates**\n   Every checklist item needs an owner and a target completion date. Ownership creates accountability; dates enable tracking.\n\n4. **Identify Dependencies and Blockers**\n   Flag items that block other work or are blocked by external factors. Surface these early so teams can unblock.\n\n5. **Define Go\u002FNo-Go Criteria**\n   Establish clear criteria for making the launch decision. What conditions must be met? Who makes the final call?\n\n6. **Document Rollback Plan**\n   Every launch should have a rollback strategy. Document how to revert if critical issues emerge post-launch.\n\n7. **Schedule Check-in Cadence**\n   Establish when the team will review checklist progress (daily standups, T-2 days review, launch day sync).\n\n## Output Format\n\nUse the template in `references\u002FTEMPLATE.md` to structure the output. A complete checklist fills every template section: Launch Overview; Engineering Readiness; QA & Testing; Design & UX; Marketing & Communications; Customer Support; Legal & Compliance; Operations & Infrastructure; Analytics & Monitoring; Go\u002FNo-Go Criteria; Rollback Plan; Check-in Schedule; and Open Issues.\n\n## Quality Checklist\n\nBefore finalizing, verify:\n\n- [ ] All functional areas are represented\n- [ ] Every item has an owner and target date\n- [ ] Blockers are clearly distinguished from nice-to-haves\n- [ ] Go\u002FNo-Go criteria are specific and measurable\n- [ ] Rollback plan is documented and tested\n- [ ] Check-in cadence is scheduled\n\n## Examples\n\nSee `references\u002FEXAMPLE.md` for a completed example.\n","\u003C!-- PM-Skills | https:\u002F\u002Fgithub.com\u002Fproduct-on-purpose\u002Fpm-skills | Apache 2.0 -->\n# Launch Checklist\n\nA launch checklist is a comprehensive verification document that ensures all functions are ready before releasing a feature or product. It coordinates across engineering, QA, design, marketing, support, legal, and operations to prevent launch-day surprises. Good launch checklists surface blockers early and create shared accountability for launch readiness.\n\n## When to Use\n\n- 1-2 weeks before any significant launch\n- During launch planning kickoff meetings\n- When coordinating cross-functional releases\n- Before major version releases or feature rollouts\n- After incidents to improve launch processes\n\n## When NOT to Use\n\n- You are validating whether to ship at all via an experiment -> use `measure-experiment-design`\n- You need the customer-facing announcement of what shipped -> use `deliver-release-notes`\n- The launch already happened and you want results or reflection -> use `measure-experiment-results` or `iterate-retrospective`\n- The change is small and single-team with no cross-functional surface: a launch checklist adds ceremony without value; track it in the sprint instead\n\n## Instructions\n\nWhen asked to create a launch checklist, follow these steps:\n\n1. **Define Launch Context**\n   Document what is launching, when, and who the key stakeholders are. Establish the launch tier (major release, minor feature, experiment) as this affects checklist scope.\n\n2. **Gather Functional Requirements**\n   For each function (engineering, QA, marketing, etc.), identify what must be complete, verified, or in place before launch. Distinguish between blockers (must-have) and nice-to-haves.\n\n3. **Assign Owners and Dates**\n   Every checklist item needs an owner and a target completion date. Ownership creates accountability; dates enable tracking.\n\n4. **Identify Dependencies and Blockers**\n   Flag items that block other work or are blocked by external factors. Surface these early so teams can unblock.\n\n5. **Define Go\u002FNo-Go Criteria**\n   Establish clear criteria for making the launch decision. What conditions must be met? Who makes the final call?\n\n6. **Document Rollback Plan**\n   Every launch should have a rollback strategy. Document how to revert if critical issues emerge post-launch.\n\n7. **Schedule Check-in Cadence**\n   Establish when the team will review checklist progress (daily standups, T-2 days review, launch day sync).\n\n## Output Format\n\nUse the template in `references\u002FTEMPLATE.md` to structure the output. A complete checklist fills every template section: Launch Overview; Engineering Readiness; QA & Testing; Design & UX; Marketing & Communications; Customer Support; Legal & Compliance; Operations & Infrastructure; Analytics & Monitoring; Go\u002FNo-Go Criteria; Rollback Plan; Check-in Schedule; and Open Issues.\n\n## Quality Checklist\n\nBefore finalizing, verify:\n\n- [ ] All functional areas are represented\n- [ ] Every item has an owner and target date\n- [ ] Blockers are clearly distinguished from nice-to-haves\n- [ ] Go\u002FNo-Go criteria are specific and measurable\n- [ ] Rollback plan is documented and tested\n- [ ] Check-in cadence is scheduled\n\n## Examples\n\nSee `references\u002FEXAMPLE.md` for a completed example.\n",{"name":5,"license":15,"metadata":24,"description":7},{"phase":25,"author":9,"updated":26,"version":27,"category":28,"frameworks":29},"deliver",1783123200000,"2.2.0","coordination",[30,31,32],"triple-diamond","lean-startup","design-thinking","main","9b920db418c5bf641edea9afb4915a286e1d42ea","skills\u002Fdeliver-launch-checklist",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":42,"prompt":52,"zipAvailable":53},[43,46,49],{"tool":44,"command":45},"npx","npx skills add product-on-purpose\u002Fpm-skills --skill deliver-launch-checklist",{"tool":47,"command":48},"bunx","bunx skills add product-on-purpose\u002Fpm-skills --skill deliver-launch-checklist",{"tool":50,"command":51},"pnpm","pnpm dlx skills add product-on-purpose\u002Fpm-skills --skill deliver-launch-checklist","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fproduct-on-purpose\u002Fpm-skills\u002Fblob\u002Fmain\u002Fskills\u002Fdeliver-launch-checklist\u002FSKILL.md",true,[55,61,65,69],{"path":56,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":59,"sourceHtmlUrl":60},"evals\u002Ftrigger-fixtures.json","REFERENCE","参考文档",4332,"https:\u002F\u002Fgithub.com\u002Fproduct-on-purpose\u002Fpm-skills\u002Fblob\u002Fmain\u002Fskills\u002Fdeliver-launch-checklist\u002Fevals\u002Ftrigger-fixtures.json",{"path":62,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":63,"sourceHtmlUrl":64},"HISTORY.md",1671,"https:\u002F\u002Fgithub.com\u002Fproduct-on-purpose\u002Fpm-skills\u002Fblob\u002Fmain\u002Fskills\u002Fdeliver-launch-checklist\u002FHISTORY.md",{"path":66,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":67,"sourceHtmlUrl":68},"references\u002FEXAMPLE.md",7992,"https:\u002F\u002Fgithub.com\u002Fproduct-on-purpose\u002Fpm-skills\u002Fblob\u002Fmain\u002Fskills\u002Fdeliver-launch-checklist\u002Freferences\u002FEXAMPLE.md",{"path":70,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":71,"sourceHtmlUrl":72},"references\u002FTEMPLATE.md",5228,"https:\u002F\u002Fgithub.com\u002Fproduct-on-purpose\u002Fpm-skills\u002Fblob\u002Fmain\u002Fskills\u002Fdeliver-launch-checklist\u002Freferences\u002FTEMPLATE.md",[74,81,88,95,102,109],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"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":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"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":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},"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":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},"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":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},"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":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},"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",[],[]]