[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M727GXT92416JQ0GCWDNQ6NS":3,"skill-same:01M727GXT92416JQ0GCWDNQ6NS":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},"01M727GXT92416JQ0GCWDNQ6NS","deliver-user-stories",null,"Generates user stories in the standard persona, action, benefit story format from product requirements or feature descriptions. Use when breaking a feature into stories for sprint planning, writing tickets, or communicating scope to engineering. For testable Given\u002FWhen\u002FThen acceptance criteria on a story, use deliver-acceptance-criteria; for boundary and failure scenarios, use deliver-edge-cases.","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-user-stories\u002FSKILL.md",[],[],"2026-11-10 18:39:20",false,"---\nname: deliver-user-stories\ndescription: Generates user stories in the standard persona, action, benefit story format from product requirements or feature descriptions. Use when breaking a feature into stories for sprint planning, writing tickets, or communicating scope to engineering. For testable Given\u002FWhen\u002FThen acceptance criteria on a story, use deliver-acceptance-criteria; for boundary and failure scenarios, use deliver-edge-cases.\nlicense: Apache-2.0\nmetadata:\n  phase: deliver\n  version: \"2.1.0\"\n  updated: 2026-06-10\n  category: specification\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# User Stories\n\nUser stories are concise descriptions of functionality from the user's perspective. They capture who needs something, what they need, and why - without prescribing how to build it. Good user stories enable teams to break large features into estimable, deliverable increments while maintaining focus on user value.\n\n## When to Use\n\n- After PRD approval, when breaking down features for implementation\n- During sprint planning to create actionable work items\n- When writing tickets for engineering teams\n- When communicating requirements to stakeholders in accessible terms\n- When prioritizing a backlog based on user value\n\n## When NOT to Use\n\n- You need deeper, QA-ready Given\u002FWhen\u002FThen coverage for a single story or slice -> use `deliver-acceptance-criteria`\n- You need the feature-wide catalog of boundary conditions and failure scenarios -> use `deliver-edge-cases`\n- The feature itself is not yet specified -> use `deliver-prd` first; stories should trace back to documented requirements\n- You want refinement-session outcomes (estimates, scope decisions, open questions) -> use `iterate-refinement-notes`\n\n## Instructions\n\nWhen asked to create user stories, follow these steps:\n\n1. **Understand the Feature Context**\n   Review the PRD or feature description. Understand the overall goal, target users, and scope boundaries. User stories should trace back to documented requirements.\n\n2. **Identify User Personas**\n   Determine which users interact with this feature. Each story should be written for a specific persona, not generic \"users.\" Different personas may need different stories for the same feature.\n\n3. **Break Down by User Goal**\n   Decompose the feature into distinct user goals. Each story should deliver a complete, valuable capability - something the user can actually do when the story is done.\n\n4. **Write Story Statements**\n   Use the format: \"As a [persona], I want [action] so that [benefit].\" The benefit clause is critical - it explains why this matters and helps prioritize.\n\n5. **Define Acceptance Criteria**\n   Write specific, testable criteria using Given\u002FWhen\u002FThen format. Acceptance criteria define \"done\" - if all criteria pass, the story is complete.\n\n6. **Apply INVEST Criteria**\n   Validate each story against INVEST: Independent, Negotiable, Valuable, Estimable, Small, Testable. Revise stories that don't meet these criteria.\n\n7. **Add Context and Notes**\n   Include relevant design references, technical considerations, and dependencies. These help implementers understand the full picture.\n\n## Output Format\n\nUse the template in `references\u002FTEMPLATE.md` to structure the output. A complete output carries, per story: Story Header; User Story Statement; Context & Background; Acceptance Criteria; Design Notes; Technical Notes; Dependencies; Out of Scope; and Open Questions where any remain. Multi-story documents nest these sections under one heading per story, as the example shows.\n\n## Quality Checklist\n\nBefore finalizing, verify:\n\n- [ ] Each story follows \"As a... I want... so that...\" format\n- [ ] Stories are independent (can be built in any order)\n- [ ] Acceptance criteria use Given\u002FWhen\u002FThen format\n- [ ] Each criterion is testable (someone can verify pass\u002Ffail)\n- [ ] Stories are small enough to complete in one sprint\n- [ ] No implementation details in the story statement\n- [ ] Benefit clause explains why this matters to the user\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# User Stories\n\nUser stories are concise descriptions of functionality from the user's perspective. They capture who needs something, what they need, and why - without prescribing how to build it. Good user stories enable teams to break large features into estimable, deliverable increments while maintaining focus on user value.\n\n## When to Use\n\n- After PRD approval, when breaking down features for implementation\n- During sprint planning to create actionable work items\n- When writing tickets for engineering teams\n- When communicating requirements to stakeholders in accessible terms\n- When prioritizing a backlog based on user value\n\n## When NOT to Use\n\n- You need deeper, QA-ready Given\u002FWhen\u002FThen coverage for a single story or slice -> use `deliver-acceptance-criteria`\n- You need the feature-wide catalog of boundary conditions and failure scenarios -> use `deliver-edge-cases`\n- The feature itself is not yet specified -> use `deliver-prd` first; stories should trace back to documented requirements\n- You want refinement-session outcomes (estimates, scope decisions, open questions) -> use `iterate-refinement-notes`\n\n## Instructions\n\nWhen asked to create user stories, follow these steps:\n\n1. **Understand the Feature Context**\n   Review the PRD or feature description. Understand the overall goal, target users, and scope boundaries. User stories should trace back to documented requirements.\n\n2. **Identify User Personas**\n   Determine which users interact with this feature. Each story should be written for a specific persona, not generic \"users.\" Different personas may need different stories for the same feature.\n\n3. **Break Down by User Goal**\n   Decompose the feature into distinct user goals. Each story should deliver a complete, valuable capability - something the user can actually do when the story is done.\n\n4. **Write Story Statements**\n   Use the format: \"As a [persona], I want [action] so that [benefit].\" The benefit clause is critical - it explains why this matters and helps prioritize.\n\n5. **Define Acceptance Criteria**\n   Write specific, testable criteria using Given\u002FWhen\u002FThen format. Acceptance criteria define \"done\" - if all criteria pass, the story is complete.\n\n6. **Apply INVEST Criteria**\n   Validate each story against INVEST: Independent, Negotiable, Valuable, Estimable, Small, Testable. Revise stories that don't meet these criteria.\n\n7. **Add Context and Notes**\n   Include relevant design references, technical considerations, and dependencies. These help implementers understand the full picture.\n\n## Output Format\n\nUse the template in `references\u002FTEMPLATE.md` to structure the output. A complete output carries, per story: Story Header; User Story Statement; Context & Background; Acceptance Criteria; Design Notes; Technical Notes; Dependencies; Out of Scope; and Open Questions where any remain. Multi-story documents nest these sections under one heading per story, as the example shows.\n\n## Quality Checklist\n\nBefore finalizing, verify:\n\n- [ ] Each story follows \"As a... I want... so that...\" format\n- [ ] Stories are independent (can be built in any order)\n- [ ] Acceptance criteria use Given\u002FWhen\u002FThen format\n- [ ] Each criterion is testable (someone can verify pass\u002Ffail)\n- [ ] Stories are small enough to complete in one sprint\n- [ ] No implementation details in the story statement\n- [ ] Benefit clause explains why this matters to the user\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",1781049600000,"2.1.0","specification",[30,31,32],"triple-diamond","lean-startup","design-thinking","main","9b920db418c5bf641edea9afb4915a286e1d42ea","skills\u002Fdeliver-user-stories",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-user-stories",{"tool":47,"command":48},"bunx","bunx skills add product-on-purpose\u002Fpm-skills --skill deliver-user-stories",{"tool":50,"command":51},"pnpm","pnpm dlx skills add product-on-purpose\u002Fpm-skills --skill deliver-user-stories","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fproduct-on-purpose\u002Fpm-skills\u002Fblob\u002Fmain\u002Fskills\u002Fdeliver-user-stories\u002FSKILL.md",true,[55,61,65,69],{"path":56,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":59,"sourceHtmlUrl":60},"evals\u002Ftrigger-fixtures.json","REFERENCE","参考文档",4464,"https:\u002F\u002Fgithub.com\u002Fproduct-on-purpose\u002Fpm-skills\u002Fblob\u002Fmain\u002Fskills\u002Fdeliver-user-stories\u002Fevals\u002Ftrigger-fixtures.json",{"path":62,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":63,"sourceHtmlUrl":64},"HISTORY.md",1156,"https:\u002F\u002Fgithub.com\u002Fproduct-on-purpose\u002Fpm-skills\u002Fblob\u002Fmain\u002Fskills\u002Fdeliver-user-stories\u002FHISTORY.md",{"path":66,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":67,"sourceHtmlUrl":68},"references\u002FEXAMPLE.md",9645,"https:\u002F\u002Fgithub.com\u002Fproduct-on-purpose\u002Fpm-skills\u002Fblob\u002Fmain\u002Fskills\u002Fdeliver-user-stories\u002Freferences\u002FEXAMPLE.md",{"path":70,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":71,"sourceHtmlUrl":72},"references\u002FTEMPLATE.md",2016,"https:\u002F\u002Fgithub.com\u002Fproduct-on-purpose\u002Fpm-skills\u002Fblob\u002Fmain\u002Fskills\u002Fdeliver-user-stories\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",[],[]]