[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M749EA4HXV6PP9T3S5TTY0MC":3,"skill-same:01M749EA4HXV6PP9T3S5TTY0MC":48},{"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":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M749EA4HXV6PP9T3S5TTY0MC","wwas",null,"Create product backlog items in Why-What-Acceptance format — independent, valuable, testable items with strategic context. Use when writing structured backlog items, breaking features into work items, or using the WWA format.","phuryn\u002Fpm-skills","phuryn","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F7837354?v=4","01M727RY5RDZZWVRDN2X5F4B1W","Pawel Huryn","01M727RY6H19NE8H5PABTR7A59",27991,"MIT","https:\u002F\u002Fgithub.com\u002Fphuryn\u002Fpm-skills\u002Fblob\u002Fmain\u002Fpm-execution\u002Fskills\u002Fwwas\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: wwas\ndescription: \"Create product backlog items in Why-What-Acceptance format — independent, valuable, testable items with strategic context. Use when writing structured backlog items, breaking features into work items, or using the WWA format.\"\n---\n# Why-What-Acceptance (WWA)\n\nCreate product backlog items in Why-What-Acceptance format. Produces independent, valuable, testable items with strategic context.\n\n**Use when:** Writing backlog items, creating product increments, breaking features into work items, or communicating strategic intent to teams.\n\n**Arguments:**\n- `$PRODUCT`: The product or system name\n- `$FEATURE`: The new feature or capability\n- `$DESIGN`: Link to design files (Figma, Miro, etc.)\n- `$ASSUMPTIONS`: Key assumptions and strategic context\n\n## Step-by-Step Process\n\n1. **Define the strategic Why** - Connect work to business and team objectives\n2. **Describe the What** - Keep descriptions concise, reference designs\n3. **Write Acceptance Criteria** - High-level, not detailed specifications\n4. **Ensure independence** - Items can be developed in any order\n5. **Keep items negotiable** - Invite team conversation, not constraints\n6. **Make items valuable** - Each delivers measurable user or business value\n7. **Ensure testability** - Outcomes are observable and verifiable\n8. **Size appropriately** - Small enough for one sprint estimate\n\n## Item Template\n\n**Title:** [What will be delivered]\n\n**Why:** [1-2 sentences connecting to strategic context and team objectives]\n\n**What:** [Short description and design link. 1-2 paragraphs maximum. A reminder of discussion, not detailed specification.]\n\n**Acceptance Criteria:**\n- [Observable outcome 1]\n- [Observable outcome 2]\n- [Observable outcome 3]\n- [Observable outcome 4]\n\n## Example WWA Item\n\n**Title:** Implement Real-Time Spending Tracker\n\n**Why:** Users need immediate feedback on spending to make conscious budget decisions. This directly supports our goal to improve financial awareness and reduce overspending.\n\n**What:** Add a real-time spending tracker that updates as users log expenses. The tracker displays their current week's spending against their set budget. Designs available in [Figma link]. This is a reminder of our discussions - detailed specifications will emerge during development conversations with the team.\n\n**Acceptance Criteria:**\n- Spending totals update within 2 seconds of logging an expense\n- Budget progress is visually indicated with a progress bar\n- Users can see remaining budget amount at a glance\n- System handles multiple expense categories correctly\n\n## Output Deliverables\n\n- Complete set of backlog items for the feature\n- Each item includes Why, What, and Acceptance Criteria sections\n- Items are independent and deliverable in any order\n- Items are sized for estimation and completion in one sprint\n- Strategic context is clear for team decision-making\n- Design references are included for implementation guidance\n\n---\n\n### Further Reading\n\n- [How to Write User Stories: The Ultimate Guide](https:\u002F\u002Fwww.productcompass.pm\u002Fp\u002Fhow-to-write-user-stories)\n","# Why-What-Acceptance (WWA)\n\nCreate product backlog items in Why-What-Acceptance format. Produces independent, valuable, testable items with strategic context.\n\n**Use when:** Writing backlog items, creating product increments, breaking features into work items, or communicating strategic intent to teams.\n\n**Arguments:**\n- `$PRODUCT`: The product or system name\n- `$FEATURE`: The new feature or capability\n- `$DESIGN`: Link to design files (Figma, Miro, etc.)\n- `$ASSUMPTIONS`: Key assumptions and strategic context\n\n## Step-by-Step Process\n\n1. **Define the strategic Why** - Connect work to business and team objectives\n2. **Describe the What** - Keep descriptions concise, reference designs\n3. **Write Acceptance Criteria** - High-level, not detailed specifications\n4. **Ensure independence** - Items can be developed in any order\n5. **Keep items negotiable** - Invite team conversation, not constraints\n6. **Make items valuable** - Each delivers measurable user or business value\n7. **Ensure testability** - Outcomes are observable and verifiable\n8. **Size appropriately** - Small enough for one sprint estimate\n\n## Item Template\n\n**Title:** [What will be delivered]\n\n**Why:** [1-2 sentences connecting to strategic context and team objectives]\n\n**What:** [Short description and design link. 1-2 paragraphs maximum. A reminder of discussion, not detailed specification.]\n\n**Acceptance Criteria:**\n- [Observable outcome 1]\n- [Observable outcome 2]\n- [Observable outcome 3]\n- [Observable outcome 4]\n\n## Example WWA Item\n\n**Title:** Implement Real-Time Spending Tracker\n\n**Why:** Users need immediate feedback on spending to make conscious budget decisions. This directly supports our goal to improve financial awareness and reduce overspending.\n\n**What:** Add a real-time spending tracker that updates as users log expenses. The tracker displays their current week's spending against their set budget. Designs available in [Figma link]. This is a reminder of our discussions - detailed specifications will emerge during development conversations with the team.\n\n**Acceptance Criteria:**\n- Spending totals update within 2 seconds of logging an expense\n- Budget progress is visually indicated with a progress bar\n- Users can see remaining budget amount at a glance\n- System handles multiple expense categories correctly\n\n## Output Deliverables\n\n- Complete set of backlog items for the feature\n- Each item includes Why, What, and Acceptance Criteria sections\n- Items are independent and deliverable in any order\n- Items are sized for estimation and completion in one sprint\n- Strategic context is clear for team decision-making\n- Design references are included for implementation guidance\n\n---\n\n### Further Reading\n\n- [How to Write User Stories: The Ultimate Guide](https:\u002F\u002Fwww.productcompass.pm\u002Fp\u002Fhow-to-write-user-stories)\n",{"name":5,"description":7},"main","9af7bfd0bc47fdad43c2eaa7a43cd13918e7aaef","pm-execution\u002Fskills\u002Fwwas",2885,"https:\u002F\u002Fgithub.com\u002Fphuryn\u002Fpm-skills","https:\u002F\u002Fwww.productcompass.pm\u002Fp\u002Fpm-skills-2-red-team-ship","https:\u002F\u002Fgithub.com\u002Fphuryn","https:\u002F\u002Fwww.productcompass.pm\u002F","AI PM Coach, ex-CPO, Builder | 400K+ Follow","2026-11-09 07:10:04",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add phuryn\u002Fpm-skills --skill wwas",{"tool":40,"command":41},"bunx","bunx skills add phuryn\u002Fpm-skills --skill wwas",{"tool":43,"command":44},"pnpm","pnpm dlx skills add phuryn\u002Fpm-skills --skill wwas","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fphuryn\u002Fpm-skills\u002Fblob\u002Fmain\u002Fpm-execution\u002Fskills\u002Fwwas\u002FSKILL.md",true,[],[49,56,63,70,77,84],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":19},"01M749K1XJGDQ1FA90BGD6MJ6Z","review-resume","Comprehensive PM resume review and tailoring against 10 best practices including XYZ+S formula, keyword optimization, job-specific tailoring, and structure. Use when reviewing a PM resume, preparing for job applications, or improving resume impact.","https:\u002F\u002Fgithub.com\u002Fphuryn\u002Fpm-skills\u002Fblob\u002Fmain\u002Fpm-toolkit\u002Fskills\u002Freview-resume\u002FSKILL.md",[],[],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M749JVQ3SER9X0V501S82BRX","privacy-policy","Draft a detailed privacy policy covering data types, jurisdiction, GDPR and compliance considerations, and clauses needing legal review. Use when creating a privacy policy, updating data protection documentation, or preparing for compliance.","https:\u002F\u002Fgithub.com\u002Fphuryn\u002Fpm-skills\u002Fblob\u002Fmain\u002Fpm-toolkit\u002Fskills\u002Fprivacy-policy\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M749JRFCNDADS61HFWMBHJJD","grammar-check","Identify grammar, logical, and flow errors in text and suggest targeted fixes without rewriting the entire text. Use when proofreading content, checking writing quality, or reviewing a draft.","https:\u002F\u002Fgithub.com\u002Fphuryn\u002Fpm-skills\u002Fblob\u002Fmain\u002Fpm-toolkit\u002Fskills\u002Fgrammar-check\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M749JMXFX9KSXV4JP6J1K7QX","draft-nda","Draft a detailed Non-Disclosure Agreement between two parties covering information types, jurisdiction, and clauses needing legal review. Use when creating confidentiality agreements or preparing an NDA for a partnership.","https:\u002F\u002Fgithub.com\u002Fphuryn\u002Fpm-skills\u002Fblob\u002Fmain\u002Fpm-toolkit\u002Fskills\u002Fdraft-nda\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M749JGY34DGZ9BGFS2YCET6N","value-proposition","Design a detailed value proposition using a 6-part JTBD template — Who, Why, What before, How, What after, Alternatives. Use when creating a value proposition, analyzing customer value delivery, or articulating why customers should choose your product.","https:\u002F\u002Fgithub.com\u002Fphuryn\u002Fpm-skills\u002Fblob\u002Fmain\u002Fpm-product-strategy\u002Fskills\u002Fvalue-proposition\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M749JE27D1APC1PWWPFMF2GN","swot-analysis","Perform a detailed SWOT analysis — strengths, weaknesses, opportunities, and threats with actionable recommendations. Use when doing strategic assessment, competitive analysis, or evaluating a product or business position.","https:\u002F\u002Fgithub.com\u002Fphuryn\u002Fpm-skills\u002Fblob\u002Fmain\u002Fpm-product-strategy\u002Fskills\u002Fswot-analysis\u002FSKILL.md",[],[]]