- name
SKILL.md
El archivo de la skill permanece en el repositorio del publicador.
Pega el comando copiado en una terminal. Instala este SKILL.md en ese agente.
npx skills add product-on-purpose/pm-skills --skill deliver-acceptance-criteria -a cursor -yPega el comando copiado en una terminal. Instala este SKILL.md en ese agente.
npx skills add product-on-purpose/pm-skills --skill deliver-acceptance-criteria -a claude-code -yPega el comando copiado en una terminal. Instala este SKILL.md en ese agente.
npx skills add product-on-purpose/pm-skills --skill deliver-acceptance-criteria -a codex -yPega el comando copiado en una terminal. Instala este SKILL.md en ese agente.
npx skills add product-on-purpose/pm-skills --skill deliver-acceptance-criteria -a grok -yEnvía el mensaje copiado en un chat de Grok Bot. El Bot obtiene este SKILL.md de GitHub y lo añade a las skills que comparten todos tus Bots.
Install this skill: https://github.com/product-on-purpose/pm-skills/tree/HEAD/skills/deliver-acceptance-criteriaDel publicador
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.mdResumen general
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.
Preguntas frecuentes
Descarga skills/deliver-acceptance-criteria/SKILL.md desde el publicador, o copia la ruta y abre el repositorio. PlugMCP lista la skill y no aloja el archivo.
El publicador lo mantiene en https://github.com/product-on-purpose/pm-skills.
Claude, Cursor, Codex y Grok Build pueden leer un SKILL.md que añadas desde el repositorio del publicador. Grok Bot lo instala cuando envías en un chat el enlace a la carpeta de la skill en GitHub.