# Use-Case Acceptance Criteria

## Metadata

- ID: TEST-ACC-`id`
- Owner: Test Engineer (docs/agents/test-engineer.md)
- Contributors: Requirements Analyst (docs/agents/requirements-analyst.md)
- Reviewers: Test Architect (docs/agents/test-architect.md)
- Team: `team`
- Stakeholders: `list`
- Status: `draft/in-progress/blocked/approved/done`
- Dates: created `YYYY-MM-DD` / updated `YYYY-MM-DD` / due `YYYY-MM-DD`
- Related: UC-`id`, REQ-`id`
- Links: `paths/urls`

## Related templates

- docs/sdlc/templates/requirements/use-case-brief-template.md

## Identifier

- UC: UC-`num`

## GIVEN/WHEN/THEN Scenarios

- GIVEN `precondition`
- WHEN `action`
- THEN `observable outcome`

Add 5–10 scenarios covering main, edge, and error cases.

## Non-Functional Acceptance

- Performance: `e.g., p95 < 300ms`
- Security: `e.g., role X only`
- Reliability: `e.g., retries on failure`