claude-sense-check

---

claude-sense-check

Performing incremental Claude Sense Check on UAT backlog.

Phase 1: Read Current State

1. Find the UAT tracking file: check for docs/testing/UAT_COVERAGE.md, docs/testing/UAT_INDEX.md, or docs/testing/uat/ directory
2. Scan for Claude Sense Check sections in every test case
3. Build a work queue: cases where - [ ] Logic verified from code perspective is unchecked
4. Skip cases where the checkbox is already [x]
5. If all cases are checked, report "All UAT cases have been sense-checked" and stop

Phase 2: Pick Next Batch

From the unchecked cases, sorted by priority (critical > high > medium > low), then by ID within each priority level:

1. Select 2-5 cases that share the same module, feature area, or user flow
2. Present to the user:
   • Batch: which cases (e.g., UAT-005, UAT-006, UAT-007)
   • Area: the functional area they belong to
   • Rationale: why they belong together
   • Relevant files: source files and components expected to be involved
3. Proceed after presenting (no user confirmation needed — this is a code-only check)

Phase 3: Gather Context

Before checking any logic, collect the full picture for the batch's feature area:

1. Read all source files relevant to the batch
2. Trace the data flow for the feature area end-to-end
3. Note dependencies, shared state, API contracts, and external integrations
4. Read existing tests for the relevant code — they reveal intent and edge cases
5. Check the Covers field on each test case to identify which backlog stories are involved
6. Read the story acceptance criteria from the relevant epic/backlog file

Do NOT proceed to logic checks until you have the full picture.

Phase 4: Code Logic Check (per case)

For each case in the batch:

1. Read the test case steps and acceptance criteria carefully
2. Trace each step through the actual source code
3. For each acceptance criterion, verify:
   • The code path exists and is reachable
   • Conditionals are correct (no off-by-one, no inverted logic)
   • Data flows correctly between components
   • Error handling covers the expected failure modes
   • Edge cases mentioned in the test case are handled
4. Assign a verdict with confidence (high = full code path traced, medium = partial trace or complex logic, low = inference without full trace):
   • Pass (high/medium/low) — logic is correct, code handles the scenario properly
   • Warning (high/medium/low) — potential issue found, describe with file:line reference
   • Fail (high/medium/low) — confirmed broken, describe with file:line reference and root cause