Guide human PO through manual acceptance testing. Optional - use when PO wants manual verification before merge.
Guide human PO through manual testing (optional step).
PO decides based on:
Key: AI verify provides acceptance-test rigor. Manual testing is optional.
ls docs/stories/**/*.story.md
Guide PO:
Criterion [N]:
Given: [precondition]
When: [action]
Then: [expected]
Steps:
1. [Setup - specific]
2. [Action - specific]
3. [Verify - specific]
Use AskUserQuestion: Pass / Fail / Blocked
All pass:
### Acceptance Checks
**Status: Accepted**
AI: Passed
Manual: Passed
By: [PO]
Date: [date]
Ready for merge.
Any fail:
### Acceptance Checks
**Status: Needs Revision**
AI: Passed
Manual: Failed
Failing: Criterion N
Expected: [X]
Observed: [Y]
Fix: [action]
Return to: Implementation
Be specific: "Click Export, select CSV, verify columns" not "Test feature"
Provide context: why matters, what AI verified, where feature, how to set up
Handle failures: gather details, prioritize, update clearly
| Aspect | AI (Required) | Human (Optional) |
|---|---|---|
| Context | Isolated | Guided |
| Scope | All testable | PO chooses |
| When | After Refactor | After Code Review |
| Purpose | Objective validation | Stakeholder confidence |