[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M727GC3B1FH348HZH0GEYZEG":3,"skill-same:01M727GC3B1FH348HZH0GEYZEG":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},"01M727GC3B1FH348HZH0GEYZEG","deliver-acceptance-criteria",null,"Generates structured Given\u002FWhen\u002FThen acceptance criteria for a user story or feature slice, covering the happy path, key failure scenarios, and non-functional expectations in testable form. Use when turning requirements into verifiable scenarios for engineering handoff and QA sign-off. For a dedicated catalog of boundary conditions, error states, and recovery paths across a feature, use deliver-edge-cases; to write the stories themselves, use deliver-user-stories.","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-acceptance-criteria\u002FSKILL.md",[],[],"2026-11-10 18:39:20",false,"---\nname: deliver-acceptance-criteria\ndescription: Generates structured Given\u002FWhen\u002FThen acceptance criteria for a user story or feature slice, covering the happy path, key failure scenarios, and non-functional expectations in testable form. Use when turning requirements into verifiable scenarios for engineering handoff and QA sign-off. For a dedicated catalog of boundary conditions, error states, and recovery paths across a feature, use deliver-edge-cases; to write the stories themselves, use deliver-user-stories.\nlicense: Apache-2.0\nmetadata:\n  phase: deliver\n  version: \"1.1.1\"\n  updated: 2026-10-17\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# Acceptance Criteria\n\nAcceptance criteria define the observable behavior that must be true for a story or feature to be considered done. This skill turns feature context into concise, testable Given\u002FWhen\u002FThen scenarios that engineers and QA can verify without guessing intent.\n\n## When to Use\n\n- After a user story, PRD section, or feature slice is defined\n- When a team needs clear pass\u002Ffail conditions for implementation\n- When writing QA-ready criteria for sprint planning or handoff\n- When a story has edge cases, error paths, or non-functional expectations that should be explicit\n\n## When NOT to Use\n\n- You need the user stories themselves -> use `deliver-user-stories`; this skill deepens a story that already exists\n- You need systematic failure coverage across a whole feature -> use `deliver-edge-cases`; this skill stays story-scoped\n- There is no story or slice to bind criteria to yet -> use `deliver-prd` or `deliver-user-stories` first\n- You are defining success metrics for an experiment, not done-ness for a story -> use `measure-experiment-design`\n- The criterion is a rate over model output, such as \"90% of answers are faithful to their sources\" -> use the AI Behavior and Evaluation section of `deliver-prd`, which says a rate needs a designed sample to verify it, and what to record until one exists\n\n## Instructions\n\nWhen asked to create acceptance criteria, follow these steps:\n\n1. **Confirm the story or feature scope**\n   Identify the exact slice of work. If the scope is unclear, ask for the user story, PRD section, or feature description before drafting criteria.\n\n2. **Separate the happy path from exceptions**\n   Start with the primary success flow, then add edge cases and error states that are likely or costly if missed.\n\n3. **Write each criterion as an observable scenario**\n   Use Given\u002FWhen\u002FThen language only. Keep each criterion independently testable and avoid implementation details.\n\n4. **Cover recovery and failure behavior**\n   Describe what the user sees or can do when validation fails, a dependency is unavailable, or a save action cannot complete.\n\n5. **Include non-functional expectations**\n   Add criteria for performance, accessibility, security, reliability, or auditability when they matter to the story.\n\n6. **Avoid duplication and overlap**\n   Each criterion should test one outcome. If two criteria describe the same behavior, merge or split them until the intent is clear.\n\n7. **Review for testability**\n   Ensure a reviewer can pass or fail each criterion without interpretation. If a statement is subjective, rewrite it into a measurable outcome.\n\n## Output Contract\n\nUse `references\u002FTEMPLATE.md` as the output format. A complete response should:\n\n- Restate the feature or story context\n- Group criteria into happy path, edge cases, error states, and non-functional criteria\n- Use explicit Given\u002FWhen\u002FThen statements for each criterion\n- Note assumptions or open questions when context is incomplete\n\n## Quality Checklist\n\nBefore finalizing, verify:\n\n- [ ] The criteria map to a specific story or feature slice\n- [ ] The happy path is covered first\n- [ ] Edge cases are explicit, not implied\n- [ ] Error states include user-visible recovery behavior\n- [ ] Non-functional criteria are included when relevant\n- [ ] Each criterion is testable and has one clear outcome\n- [ ] No implementation details leak into the acceptance criteria\n\n## Examples\n\nSee `references\u002FEXAMPLE.md` for a completed example based on a realistic e-commerce checkout flow.\n","\u003C!-- PM-Skills | https:\u002F\u002Fgithub.com\u002Fproduct-on-purpose\u002Fpm-skills | Apache 2.0 -->\n# Acceptance Criteria\n\nAcceptance criteria define the observable behavior that must be true for a story or feature to be considered done. This skill turns feature context into concise, testable Given\u002FWhen\u002FThen scenarios that engineers and QA can verify without guessing intent.\n\n## When to Use\n\n- After a user story, PRD section, or feature slice is defined\n- When a team needs clear pass\u002Ffail conditions for implementation\n- When writing QA-ready criteria for sprint planning or handoff\n- When a story has edge cases, error paths, or non-functional expectations that should be explicit\n\n## When NOT to Use\n\n- You need the user stories themselves -> use `deliver-user-stories`; this skill deepens a story that already exists\n- You need systematic failure coverage across a whole feature -> use `deliver-edge-cases`; this skill stays story-scoped\n- There is no story or slice to bind criteria to yet -> use `deliver-prd` or `deliver-user-stories` first\n- You are defining success metrics for an experiment, not done-ness for a story -> use `measure-experiment-design`\n- The criterion is a rate over model output, such as \"90% of answers are faithful to their sources\" -> use the AI Behavior and Evaluation section of `deliver-prd`, which says a rate needs a designed sample to verify it, and what to record until one exists\n\n## Instructions\n\nWhen asked to create acceptance criteria, follow these steps:\n\n1. **Confirm the story or feature scope**\n   Identify the exact slice of work. If the scope is unclear, ask for the user story, PRD section, or feature description before drafting criteria.\n\n2. **Separate the happy path from exceptions**\n   Start with the primary success flow, then add edge cases and error states that are likely or costly if missed.\n\n3. **Write each criterion as an observable scenario**\n   Use Given\u002FWhen\u002FThen language only. Keep each criterion independently testable and avoid implementation details.\n\n4. **Cover recovery and failure behavior**\n   Describe what the user sees or can do when validation fails, a dependency is unavailable, or a save action cannot complete.\n\n5. **Include non-functional expectations**\n   Add criteria for performance, accessibility, security, reliability, or auditability when they matter to the story.\n\n6. **Avoid duplication and overlap**\n   Each criterion should test one outcome. If two criteria describe the same behavior, merge or split them until the intent is clear.\n\n7. **Review for testability**\n   Ensure a reviewer can pass or fail each criterion without interpretation. If a statement is subjective, rewrite it into a measurable outcome.\n\n## Output Contract\n\nUse `references\u002FTEMPLATE.md` as the output format. A complete response should:\n\n- Restate the feature or story context\n- Group criteria into happy path, edge cases, error states, and non-functional criteria\n- Use explicit Given\u002FWhen\u002FThen statements for each criterion\n- Note assumptions or open questions when context is incomplete\n\n## Quality Checklist\n\nBefore finalizing, verify:\n\n- [ ] The criteria map to a specific story or feature slice\n- [ ] The happy path is covered first\n- [ ] Edge cases are explicit, not implied\n- [ ] Error states include user-visible recovery behavior\n- [ ] Non-functional criteria are included when relevant\n- [ ] Each criterion is testable and has one clear outcome\n- [ ] No implementation details leak into the acceptance criteria\n\n## Examples\n\nSee `references\u002FEXAMPLE.md` for a completed example based on a realistic e-commerce checkout flow.\n",{"name":5,"license":15,"metadata":24,"description":7},{"phase":25,"author":9,"updated":26,"version":27,"category":28,"frameworks":29},"deliver",1792195200000,"1.1.1","specification",[30,31,32],"triple-diamond","lean-startup","design-thinking","main","9b920db418c5bf641edea9afb4915a286e1d42ea","skills\u002Fdeliver-acceptance-criteria",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-acceptance-criteria",{"tool":47,"command":48},"bunx","bunx skills add product-on-purpose\u002Fpm-skills --skill deliver-acceptance-criteria",{"tool":50,"command":51},"pnpm","pnpm dlx skills add product-on-purpose\u002Fpm-skills --skill deliver-acceptance-criteria","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fproduct-on-purpose\u002Fpm-skills\u002Fblob\u002Fmain\u002Fskills\u002Fdeliver-acceptance-criteria\u002FSKILL.md",true,[55,61,65,69,73],{"path":56,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":59,"sourceHtmlUrl":60},"evals\u002Foutput-scenarios\u002Fbulk-invite.md","REFERENCE","参考文档",1928,"https:\u002F\u002Fgithub.com\u002Fproduct-on-purpose\u002Fpm-skills\u002Fblob\u002Fmain\u002Fskills\u002Fdeliver-acceptance-criteria\u002Fevals\u002Foutput-scenarios\u002Fbulk-invite.md",{"path":62,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":63,"sourceHtmlUrl":64},"evals\u002Ftrigger-fixtures.json",4344,"https:\u002F\u002Fgithub.com\u002Fproduct-on-purpose\u002Fpm-skills\u002Fblob\u002Fmain\u002Fskills\u002Fdeliver-acceptance-criteria\u002Fevals\u002Ftrigger-fixtures.json",{"path":66,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":67,"sourceHtmlUrl":68},"HISTORY.md",2004,"https:\u002F\u002Fgithub.com\u002Fproduct-on-purpose\u002Fpm-skills\u002Fblob\u002Fmain\u002Fskills\u002Fdeliver-acceptance-criteria\u002FHISTORY.md",{"path":70,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":71,"sourceHtmlUrl":72},"references\u002FEXAMPLE.md",2855,"https:\u002F\u002Fgithub.com\u002Fproduct-on-purpose\u002Fpm-skills\u002Fblob\u002Fmain\u002Fskills\u002Fdeliver-acceptance-criteria\u002Freferences\u002FEXAMPLE.md",{"path":74,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":75,"sourceHtmlUrl":76},"references\u002FTEMPLATE.md",1668,"https:\u002F\u002Fgithub.com\u002Fproduct-on-purpose\u002Fpm-skills\u002Fblob\u002Fmain\u002Fskills\u002Fdeliver-acceptance-criteria\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",[],[]]