[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M727G8HW8DQCW2QXFWQ0XKCD":3,"skill-same:01M727G8HW8DQCW2QXFWQ0XKCD":77},{"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},"01M727G8HW8DQCW2QXFWQ0XKCD","define-problem-statement",null,"Creates a clear problem framing document with user impact, business context, and success criteria. Use when starting a new initiative, realigning a drifted project, or communicating up to leadership.","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\u002Fdefine-problem-statement\u002FSKILL.md",[],[],"2026-11-10 18:39:20",false,"---\nname: define-problem-statement\ndescription: Creates a clear problem framing document with user impact, business context, and success criteria. Use when starting a new initiative, realigning a drifted project, or communicating up to leadership.\nlicense: Apache-2.0\nmetadata:\n  phase: define\n  version: \"2.1.0\"\n  updated: 2026-06-10\n  category: problem-framing\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# Problem Statement\n\nA problem statement is a concise document that frames the problem you're solving, articulates the impact on users and the business, and defines clear success criteria. It serves as the foundation for all subsequent product work by ensuring alignment on *what* problem to solve before jumping to *how* to solve it.\n\n## When to Use\n\n- Starting a new initiative or project to establish shared understanding\n- Realigning a drifted project back to its original intent\n- Communicating up to leadership or stakeholders about priorities\n- Evaluating whether a proposed solution actually addresses the core problem\n- Onboarding new team members to provide context\n\n## When NOT to Use\n\n- The problem is already agreed and engineering needs the spec -> use `deliver-prd`\n- You want to propose and compare solution approaches -> use `develop-solution-brief`\n- You are capturing customer motivation rather than a business problem -> use `define-jtbd-canvas`\n- The \"problem\" is really an unvalidated assumption -> frame it with `define-hypothesis` and test it before committing a team to it\n\n## Instructions\n\nWhen asked to create a problem statement, follow these steps:\n\n1. **Identify the User Segment**\n   Ask who is experiencing this problem. Get specific about the user persona, role, or segment. Avoid vague descriptions like \"users\" - instead target \"mobile shoppers completing checkout\" or \"enterprise admins managing 50+ users.\"\n\n2. **Understand the Pain Points**\n   Explore what friction, frustration, or unmet need the user experiences. Ask probing questions to understand the severity and frequency of the problem. Look for evidence from user research, support tickets, or behavioral data.\n\n3. **Establish Business Context**\n   Connect the user problem to business impact. How does this problem affect revenue, retention, growth, or strategic goals? Why should the organization invest in solving this now versus later?\n\n4. **Define Success Metrics**\n   Identify how you will measure success. What metrics will move if this problem is solved? Establish current baselines and target improvements. Be specific and time-bound.\n\n5. **Surface Constraints and Considerations**\n   Note any technical limitations, resource constraints, regulatory requirements, or dependencies that will shape the solution space.\n\n6. **Capture Open Questions**\n   Document what you don't know yet. What assumptions need validation? What additional research is needed?\n\n## Output Format\n\nUse the template in `references\u002FTEMPLATE.md` to structure the output. A complete problem statement fills every template section: Problem Summary; User Impact; Business Context; Success Criteria; Constraints & Considerations; and Open Questions.\n\n## Quality Checklist\n\nBefore finalizing, verify:\n\n- [ ] Problem is specific to a defined user segment (not \"all users\")\n- [ ] Impact is quantified with data or reasonable estimates\n- [ ] Success metrics have baselines and targets\n- [ ] Problem describes the \"what\" without prescribing the \"how\"\n- [ ] Business context explains why this matters now\n- [ ] Open questions are captured for follow-up\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# Problem Statement\n\nA problem statement is a concise document that frames the problem you're solving, articulates the impact on users and the business, and defines clear success criteria. It serves as the foundation for all subsequent product work by ensuring alignment on *what* problem to solve before jumping to *how* to solve it.\n\n## When to Use\n\n- Starting a new initiative or project to establish shared understanding\n- Realigning a drifted project back to its original intent\n- Communicating up to leadership or stakeholders about priorities\n- Evaluating whether a proposed solution actually addresses the core problem\n- Onboarding new team members to provide context\n\n## When NOT to Use\n\n- The problem is already agreed and engineering needs the spec -> use `deliver-prd`\n- You want to propose and compare solution approaches -> use `develop-solution-brief`\n- You are capturing customer motivation rather than a business problem -> use `define-jtbd-canvas`\n- The \"problem\" is really an unvalidated assumption -> frame it with `define-hypothesis` and test it before committing a team to it\n\n## Instructions\n\nWhen asked to create a problem statement, follow these steps:\n\n1. **Identify the User Segment**\n   Ask who is experiencing this problem. Get specific about the user persona, role, or segment. Avoid vague descriptions like \"users\" - instead target \"mobile shoppers completing checkout\" or \"enterprise admins managing 50+ users.\"\n\n2. **Understand the Pain Points**\n   Explore what friction, frustration, or unmet need the user experiences. Ask probing questions to understand the severity and frequency of the problem. Look for evidence from user research, support tickets, or behavioral data.\n\n3. **Establish Business Context**\n   Connect the user problem to business impact. How does this problem affect revenue, retention, growth, or strategic goals? Why should the organization invest in solving this now versus later?\n\n4. **Define Success Metrics**\n   Identify how you will measure success. What metrics will move if this problem is solved? Establish current baselines and target improvements. Be specific and time-bound.\n\n5. **Surface Constraints and Considerations**\n   Note any technical limitations, resource constraints, regulatory requirements, or dependencies that will shape the solution space.\n\n6. **Capture Open Questions**\n   Document what you don't know yet. What assumptions need validation? What additional research is needed?\n\n## Output Format\n\nUse the template in `references\u002FTEMPLATE.md` to structure the output. A complete problem statement fills every template section: Problem Summary; User Impact; Business Context; Success Criteria; Constraints & Considerations; and Open Questions.\n\n## Quality Checklist\n\nBefore finalizing, verify:\n\n- [ ] Problem is specific to a defined user segment (not \"all users\")\n- [ ] Impact is quantified with data or reasonable estimates\n- [ ] Success metrics have baselines and targets\n- [ ] Problem describes the \"what\" without prescribing the \"how\"\n- [ ] Business context explains why this matters now\n- [ ] Open questions are captured for follow-up\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},"define",1781049600000,"2.1.0","problem-framing",[30,31,32],"triple-diamond","lean-startup","design-thinking","main","9b920db418c5bf641edea9afb4915a286e1d42ea","skills\u002Fdefine-problem-statement",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 define-problem-statement",{"tool":47,"command":48},"bunx","bunx skills add product-on-purpose\u002Fpm-skills --skill define-problem-statement",{"tool":50,"command":51},"pnpm","pnpm dlx skills add product-on-purpose\u002Fpm-skills --skill define-problem-statement","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fproduct-on-purpose\u002Fpm-skills\u002Fblob\u002Fmain\u002Fskills\u002Fdefine-problem-statement\u002FSKILL.md",true,[55,61,65,69,73],{"path":56,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":59,"sourceHtmlUrl":60},"evals\u002Foutput-scenarios\u002Fcheckout-abandonment.md","REFERENCE","参考文档",1992,"https:\u002F\u002Fgithub.com\u002Fproduct-on-purpose\u002Fpm-skills\u002Fblob\u002Fmain\u002Fskills\u002Fdefine-problem-statement\u002Fevals\u002Foutput-scenarios\u002Fcheckout-abandonment.md",{"path":62,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":63,"sourceHtmlUrl":64},"evals\u002Ftrigger-fixtures.json",4396,"https:\u002F\u002Fgithub.com\u002Fproduct-on-purpose\u002Fpm-skills\u002Fblob\u002Fmain\u002Fskills\u002Fdefine-problem-statement\u002Fevals\u002Ftrigger-fixtures.json",{"path":66,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":67,"sourceHtmlUrl":68},"HISTORY.md",731,"https:\u002F\u002Fgithub.com\u002Fproduct-on-purpose\u002Fpm-skills\u002Fblob\u002Fmain\u002Fskills\u002Fdefine-problem-statement\u002FHISTORY.md",{"path":70,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":71,"sourceHtmlUrl":72},"references\u002FEXAMPLE.md",4095,"https:\u002F\u002Fgithub.com\u002Fproduct-on-purpose\u002Fpm-skills\u002Fblob\u002Fmain\u002Fskills\u002Fdefine-problem-statement\u002Freferences\u002FEXAMPLE.md",{"path":74,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":75,"sourceHtmlUrl":76},"references\u002FTEMPLATE.md",1727,"https:\u002F\u002Fgithub.com\u002Fproduct-on-purpose\u002Fpm-skills\u002Fblob\u002Fmain\u002Fskills\u002Fdefine-problem-statement\u002Freferences\u002FTEMPLATE.md",[78,85,92,99,106,113],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"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":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"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":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"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":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"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":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":110,"categories":111,"keywords":112,"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":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":119,"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",[],[]]