AGENT SKILL

deliver-acceptance-criteria

Generates structured Given/When/Then 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.

License 许可
Apache-2.0
最近更新
2026-11-14
Stars
★ 805
Forks
102

01 前言 Front Matter

name
deliver-acceptance-criteria
license
Apache-2.0
metadata
{ "phase": "deliver", "author": "product-on-purpose", "updated": 1792195200000, "version": "1.1.1", "category": "specification", "frameworks": [ "triple-diamond", "lean-startup", "design-thinking" ] }
description
Generates structured Given/When/Then 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.

02 资源文件 5

03 SKILL.md 正文

<!-- PM-Skills | https://github.com/product-on-purpose/pm-skills | Apache 2.0 -->

Acceptance Criteria

Acceptance 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/When/Then scenarios that engineers and QA can verify without guessing intent.

When to Use

  • After a user story, PRD section, or feature slice is defined
  • When a team needs clear pass/fail conditions for implementation
  • When writing QA-ready criteria for sprint planning or handoff
  • When a story has edge cases, error paths, or non-functional expectations that should be explicit

When NOT to Use

  • You need the user stories themselves -> use deliver-user-stories; this skill deepens a story that already exists
  • You need systematic failure coverage across a whole feature -> use deliver-edge-cases; this skill stays story-scoped
  • There is no story or slice to bind criteria to yet -> use deliver-prd or deliver-user-stories first
  • You are defining success metrics for an experiment, not done-ness for a story -> use measure-experiment-design
  • 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

Instructions

When asked to create acceptance criteria, follow these steps:

  1. Confirm the story or feature scope Identify the exact slice of work. If the scope is unclear, ask for the user story, PRD section, or feature description before drafting criteria.

  2. Separate the happy path from exceptions Start with the primary success flow, then add edge cases and error states that are likely or costly if missed.

  3. Write each criterion as an observable scenario Use Given/When/Then language only. Keep each criterion independently testable and avoid implementation details.

  4. Cover recovery and failure behavior Describe what the user sees or can do when validation fails, a dependency is unavailable, or a save action cannot complete.

  5. Include non-functional expectations Add criteria for performance, accessibility, security, reliability, or auditability when they matter to the story.

  6. Avoid duplication and overlap Each criterion should test one outcome. If two criteria describe the same behavior, merge or split them until the intent is clear.

  7. Review for testability Ensure a reviewer can pass or fail each criterion without interpretation. If a statement is subjective, rewrite it into a measurable outcome.

Output Contract

Use references/TEMPLATE.md as the output format. A complete response should:

  • Restate the feature or story context
  • Group criteria into happy path, edge cases, error states, and non-functional criteria
  • Use explicit Given/When/Then statements for each criterion
  • Note assumptions or open questions when context is incomplete

Quality Checklist

Before finalizing, verify:

  • [ ] The criteria map to a specific story or feature slice
  • [ ] The happy path is covered first
  • [ ] Edge cases are explicit, not implied
  • [ ] Error states include user-visible recovery behavior
  • [ ] Non-functional criteria are included when relevant
  • [ ] Each criterion is testable and has one clear outcome
  • [ ] No implementation details leak into the acceptance criteria

Examples

See references/EXAMPLE.md for a completed example based on a realistic e-commerce checkout flow.

04 同仓库更多 Skills

product-on-purpose
product-on-purpose/pm-skills

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.

★ 805
product-on-purpose
product-on-purpose/pm-skills

utility-slideshow-creator

Generates professional presentations from a JSON deck specification using 18 slide types with dark/light variants, content-to-layout decision logic, and calibrated character limits. Ships with a default professional theme.

★ 805
product-on-purpose
product-on-purpose/pm-skills

utility-pm-workflow-orchestrator

Run an ordered sequence of pm-skills against one input, pausing for go/no-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.

★ 805
product-on-purpose
product-on-purpose/pm-skills

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.

★ 805
product-on-purpose
product-on-purpose/pm-skills

utility-pm-skill-validate

Audits an existing pm-skills skill against structural conventions and quality criteria. Produces a structured validation report with pass/fail checks, severity-graded findings, and actionable recommendations. Use when checking whether a skill meets repo standards before shipping or after making changes.

★ 805
product-on-purpose
product-on-purpose/pm-skills

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.

★ 805