- name
SKILL.md
The skill file stays in the publisher's repository.
Paste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add product-on-purpose/pm-skills --skill deliver-acceptance-criteria -a cursor -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add product-on-purpose/pm-skills --skill deliver-acceptance-criteria -a claude-code -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add product-on-purpose/pm-skills --skill deliver-acceptance-criteria -a codex -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add product-on-purpose/pm-skills --skill deliver-acceptance-criteria -a grok -ySend the copied message in a Grok Bot chat. The Bot fetches this SKILL.md from GitHub and adds it to the skills all your Bots share.
Install this skill: https://github.com/product-on-purpose/pm-skills/tree/HEAD/skills/deliver-acceptance-criteriaFrom the publisher
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.
deliver-user-stories; this skill deepens a story that already existsdeliver-edge-cases; this skill stays story-scopeddeliver-prd or deliver-user-stories firstmeasure-experiment-designdeliver-prd, which says a rate needs a designed sample to verify it, and what to record until one existsWhen asked to create acceptance criteria, follow these steps:
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.
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.
Write each criterion as an observable scenario Use Given/When/Then language only. Keep each criterion independently testable and avoid implementation details.
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.
Include non-functional expectations Add criteria for performance, accessibility, security, reliability, or auditability when they matter to the story.
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.
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.
Use references/TEMPLATE.md as the output format. A complete response should:
Before finalizing, verify:
See references/EXAMPLE.md for a completed example based on a realistic e-commerce checkout flow.
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 t
---name: deliver-acceptance-criteriadescription: Generates structured Given/When/Then acceptance criteria for a user story or feature slice, covering the happy…---# skills/deliver-acceptance-criteria/SKILL.mdOverview
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.
FAQ
Download skills/deliver-acceptance-criteria/SKILL.md from the publisher, or copy the path and open the repository. PlugMCP lists the skill and does not host the file.
The publisher keeps it at https://github.com/product-on-purpose/pm-skills.
Claude, Cursor, Codex, and Grok Build can read a SKILL.md you add from the publisher's repository. Grok Bot installs it when you send the skill's GitHub folder link in a chat.