[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M727FSYKQ9WHAKX13HZPXBCB":3,"skill-same:01M727FSYKQ9WHAKX13HZPXBCB":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},"01M727FSYKQ9WHAKX13HZPXBCB","define-hypothesis",null,"Defines a testable hypothesis with clear success metrics and a validation approach. Use when forming assumptions to test or aligning a team on what success looks like, before any experiment is designed. To design the A\u002FB test or experiment that will validate the hypothesis, use measure-experiment-design.","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-hypothesis\u002FSKILL.md",[],[],"2026-11-10 18:39:20",false,"---\nname: define-hypothesis\ndescription: Defines a testable hypothesis with clear success metrics and a validation approach. Use when forming assumptions to test or aligning a team on what success looks like, before any experiment is designed. To design the A\u002FB test or experiment that will validate the hypothesis, use measure-experiment-design.\nlicense: Apache-2.0\nmetadata:\n  phase: define\n  version: \"2.1.0\"\n  updated: 2026-06-10\n  category: ideation\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# Hypothesis\n\nA hypothesis is a testable prediction about how a change will affect user behavior or business outcomes. It transforms assumptions into explicit statements that can be validated or invalidated through experimentation. Well-formed hypotheses prevent teams from building features based on untested beliefs and create shared understanding of what success looks like.\n\n## When to Use\n\n- After problem framing, before committing to a solution\n- When designing experiments or A\u002FB tests\n- When team members have differing assumptions about user behavior\n- Before investing significant engineering resources in a feature\n- When pivoting direction and need to validate the new approach\n\n## When NOT to Use\n\n- You are ready to design the actual A\u002FB test (variants, sample size, duration) -> use `measure-experiment-design`; this skill frames what to test, not how\n- The problem itself is still unframed -> use `define-problem-statement` first\n- You want to organize many assumptions and ideas into a discovery structure -> use `define-opportunity-tree`\n- The team needs the full business-model picture, not one testable claim -> use `foundation-lean-canvas`\n\n## Instructions\n\nWhen asked to create a hypothesis, follow these steps:\n\n1. **State the Belief**\n   Articulate what you believe will happen. Use the structured format: \"We believe that [action\u002Fchange] for [target user] will [expected outcome].\" Be specific about the intervention - vague hypotheses can't be tested.\n\n2. **Identify the Target User**\n   Define who this hypothesis applies to. A hypothesis about \"users\" is too broad. Specify the segment: new users in their first week, power users with 10+ sessions, churned users returning, etc.\n\n3. **Define the Expected Outcome**\n   What behavior change or result do you expect? Frame it in terms of user actions (complete onboarding, make a purchase, return within 7 days) rather than internal metrics when possible.\n\n4. **Set Success Metrics**\n   Choose a primary metric that directly measures the expected outcome. Include secondary metrics that provide context and guardrail metrics that ensure you're not causing harm elsewhere.\n\n5. **Describe Validation Approach**\n   How will you test this hypothesis? A\u002FB test, user interviews, prototype testing, cohort analysis? Be specific about sample size, duration, and statistical requirements.\n\n6. **Document Risks and Assumptions**\n   What could invalidate this hypothesis beyond the test results? What are you assuming to be true that you haven't validated?\n\n## Output Format\n\nUse the template in `references\u002FTEMPLATE.md` to structure the output. A complete hypothesis document fills every template section: Hypothesis Statement; Background & Rationale; Target User Segment; Success Metrics; Validation Approach; Risks & Assumptions; and Timeline.\n\n## Quality Checklist\n\nBefore finalizing, verify:\n\n- [ ] Hypothesis is falsifiable (possible to prove wrong)\n- [ ] Success metric has a specific numeric target\n- [ ] Target user segment is clearly defined\n- [ ] Validation approach is practical and time-bound\n- [ ] Pass\u002Ffail criteria are unambiguous\n- [ ] Hypothesis doesn't assume the solution works\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# Hypothesis\n\nA hypothesis is a testable prediction about how a change will affect user behavior or business outcomes. It transforms assumptions into explicit statements that can be validated or invalidated through experimentation. Well-formed hypotheses prevent teams from building features based on untested beliefs and create shared understanding of what success looks like.\n\n## When to Use\n\n- After problem framing, before committing to a solution\n- When designing experiments or A\u002FB tests\n- When team members have differing assumptions about user behavior\n- Before investing significant engineering resources in a feature\n- When pivoting direction and need to validate the new approach\n\n## When NOT to Use\n\n- You are ready to design the actual A\u002FB test (variants, sample size, duration) -> use `measure-experiment-design`; this skill frames what to test, not how\n- The problem itself is still unframed -> use `define-problem-statement` first\n- You want to organize many assumptions and ideas into a discovery structure -> use `define-opportunity-tree`\n- The team needs the full business-model picture, not one testable claim -> use `foundation-lean-canvas`\n\n## Instructions\n\nWhen asked to create a hypothesis, follow these steps:\n\n1. **State the Belief**\n   Articulate what you believe will happen. Use the structured format: \"We believe that [action\u002Fchange] for [target user] will [expected outcome].\" Be specific about the intervention - vague hypotheses can't be tested.\n\n2. **Identify the Target User**\n   Define who this hypothesis applies to. A hypothesis about \"users\" is too broad. Specify the segment: new users in their first week, power users with 10+ sessions, churned users returning, etc.\n\n3. **Define the Expected Outcome**\n   What behavior change or result do you expect? Frame it in terms of user actions (complete onboarding, make a purchase, return within 7 days) rather than internal metrics when possible.\n\n4. **Set Success Metrics**\n   Choose a primary metric that directly measures the expected outcome. Include secondary metrics that provide context and guardrail metrics that ensure you're not causing harm elsewhere.\n\n5. **Describe Validation Approach**\n   How will you test this hypothesis? A\u002FB test, user interviews, prototype testing, cohort analysis? Be specific about sample size, duration, and statistical requirements.\n\n6. **Document Risks and Assumptions**\n   What could invalidate this hypothesis beyond the test results? What are you assuming to be true that you haven't validated?\n\n## Output Format\n\nUse the template in `references\u002FTEMPLATE.md` to structure the output. A complete hypothesis document fills every template section: Hypothesis Statement; Background & Rationale; Target User Segment; Success Metrics; Validation Approach; Risks & Assumptions; and Timeline.\n\n## Quality Checklist\n\nBefore finalizing, verify:\n\n- [ ] Hypothesis is falsifiable (possible to prove wrong)\n- [ ] Success metric has a specific numeric target\n- [ ] Target user segment is clearly defined\n- [ ] Validation approach is practical and time-bound\n- [ ] Pass\u002Ffail criteria are unambiguous\n- [ ] Hypothesis doesn't assume the solution works\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","ideation",[30,31,32],"triple-diamond","lean-startup","design-thinking","main","9b920db418c5bf641edea9afb4915a286e1d42ea","skills\u002Fdefine-hypothesis",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-hypothesis",{"tool":47,"command":48},"bunx","bunx skills add product-on-purpose\u002Fpm-skills --skill define-hypothesis",{"tool":50,"command":51},"pnpm","pnpm dlx skills add product-on-purpose\u002Fpm-skills --skill define-hypothesis","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fproduct-on-purpose\u002Fpm-skills\u002Fblob\u002Fmain\u002Fskills\u002Fdefine-hypothesis\u002FSKILL.md",true,[55,61,65,69],{"path":56,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":59,"sourceHtmlUrl":60},"evals\u002Ftrigger-fixtures.json","REFERENCE","参考文档",4470,"https:\u002F\u002Fgithub.com\u002Fproduct-on-purpose\u002Fpm-skills\u002Fblob\u002Fmain\u002Fskills\u002Fdefine-hypothesis\u002Fevals\u002Ftrigger-fixtures.json",{"path":62,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":63,"sourceHtmlUrl":64},"HISTORY.md",1153,"https:\u002F\u002Fgithub.com\u002Fproduct-on-purpose\u002Fpm-skills\u002Fblob\u002Fmain\u002Fskills\u002Fdefine-hypothesis\u002FHISTORY.md",{"path":66,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":67,"sourceHtmlUrl":68},"references\u002FEXAMPLE.md",5799,"https:\u002F\u002Fgithub.com\u002Fproduct-on-purpose\u002Fpm-skills\u002Fblob\u002Fmain\u002Fskills\u002Fdefine-hypothesis\u002Freferences\u002FEXAMPLE.md",{"path":70,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":71,"sourceHtmlUrl":72},"references\u002FTEMPLATE.md",2837,"https:\u002F\u002Fgithub.com\u002Fproduct-on-purpose\u002Fpm-skills\u002Fblob\u002Fmain\u002Fskills\u002Fdefine-hypothesis\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",[],[]]