Define systematic, portable verification checklists for common operations within a specific domain.
When to Use
- Establishing a new verification protocol for a specific component.
- Ensuring consistent quality gates across different implementations.
- Automating manual verification steps into a structured checklist.
Verification Checklist
[Operation Name]
- Requirement 1: [Description of success criteria]
- Requirement 2: [Description of success criteria]
- Edge Case 1: [Description of how to verify]
[Data Integrity]
- Roundtrip: [Verify data matches after save/load]
- Schema: [Verify output adheres to expected schema]
[Security/Safety]
- Permission: [Verify restricted access works as intended]
- Sanitization: [Verify inputs are correctly handled]
Process
- Identify Operation: What specific action needs verification?
- Define Success: What does a "perfect" execution look like?
- Draft Checklist: Use the categories above to list specific checks.
- Test Checklist: Run through the checks on a real instance.
- Iterate: Refine the checklist based on discovered edge cases.
Rationalizations
| Rationalization | Reality |
|---|---|
| "This is a minor change, full verification is overkill" | Every change needs verification to prevent regressions. |
| "I've tested this manually already" | Manual testing is prone to oversight; structured checklists ensure consistency. |
Red Flags
- Skipping verification steps for "simple" changes
- Marking items as complete without actually performing the check
- Relying solely on successful build/lint without functional verification
References
AGENTS.md- Repository standards and quality gatesscripts/quality_gate.sh- Automated verification entry point