02-acceptance-criteria
Installation
SKILL.md
Acceptance Criteria Skill Guidance
Use When
- formalising deterministic Given-When-Then acceptance criteria for existing user stories; use user-story-generation when the backlog or personas have not yet been defined.
- Use this procedure when the required source artefacts are available and
Acceptance-criteria catalogueis the next lifecycle deliverable.
Do Not Use When
- Use
user-story-generationwhen that neighbouring route owns the decision or deliverable. - Do not invent missing project evidence, standards clauses, thresholds, or stakeholder decisions.
Required Inputs
| Artefact | Source or provider | Required? | Behaviour when missing |
|---|---|---|---|
| Approved user stories, business rules, quality thresholds, and error cases | Product owner, requirements baseline, and domain references | Yes | Stop the affected step, name the missing source, and return only a qualified gap record. |