verification-before-completion

Verification Before Completion

The Iron Law

NO COMPLETION CLAIMS WITHOUT FRESH VERIFICATION EVIDENCE

Never claim work is complete, fixed, passing, or ready without:

1. Running the verification command
2. Reading the actual output
3. Confirming it matches your claim

TDD Enforcement (Implementation Tasks)

For ANY implementation task (new feature, component, handler, schema):

TDD is NOT optional for:

• New components (React components, hooks)
• New data provider handlers
• New Zod schemas
• New service classes
• Bug fixes (regression test first)

TDD Red Flags - STOP if you're about to:

• Write implementation code without a test file
• Say "I'll add tests later"
• Skip the failing test phase
• Implement multiple features before testing

Manual E2E for UI Changes

For ANY UI-facing change, offer Manual E2E Testing:

When implementing UI changes (forms, lists, slide-overs, buttons), remind user:

Manual E2E Available: This UI change can be verified using Claude Chrome. See docs/tests/e2e/ for existing test prompts or I can generate a new one.

Would you like me to generate a Claude Chrome test prompt for this feature?

When to generate E2E prompts:

• New forms (CRUD create/edit)
• New validation rules
• UI workflow changes
• Accessibility improvements
• Any user-facing feature

The 5-Step Gate

Before ANY completion claim:

Skip any step = lying, not verifying

Crispy CRM Verification Commands

Red Flags - STOP

If you're about to say ANY of these, STOP and verify:

Rationalization Prevention

Correct Patterns

Build Verification

✅ CORRECT:
[Run: npm run build]
[See: exit 0, no errors]
"Build passes - exit 0, compiled successfully"

❌ WRONG:
"Build should pass now"
"The code looks correct"
"I fixed the error so it works"

TypeScript Verification

✅ CORRECT:
[Run: npx tsc --noEmit]
[See: no output (means success)]
"TypeScript check passes - 0 errors"

❌ WRONG:
"Types look correct"
"Fixed the type error"
"Should compile now"

Feature Completion

✅ CORRECT:
Requirements checklist:
- [x] User can create contact (verified via test)
- [x] Validation shows errors (verified via build)
- [x] Form saves to database (verified via E2E)
"Feature complete - all 3 requirements verified"

❌ WRONG:
"Feature is complete"
"All requirements implemented"
"Ready for review"

Git Operations

✅ CORRECT:
[Run: npm run build] → exit 0
[Run: npx tsc --noEmit] → 0 errors
"Ready to commit - build and types verified"

❌ WRONG:
"Ready to commit"
"Can push now"
"PR is ready"

When This Applies

ALWAYS before:

• Claiming tests pass
• Claiming build succeeds
• Claiming types are correct
• Claiming bug is fixed
• Claiming feature is complete
• Claiming ready for commit/PR/push
• Any variation of "done", "works", "fixed"

Rule applies to:

• Exact phrases ("tests pass")
• Paraphrases ("specs are green")
• Implications ("we're good to go")
• Any positive statement about work state

The Bottom Line

No shortcuts for verification. Run the command. Read the output. THEN claim the result. This is non-negotiable.

Evidence before claims, always.