aposd-verifying-correctness

name

aposd-verifying-correctness

description

Verify code correctness before claiming done or committing. Run 6-dimension checklist: requirements coverage, concurrency safety, error handling, resource management, boundary conditions, and security. Output PASS/FAIL per dimension with final DONE/NOT DONE verdict. Use after implementation as pre-commit gate. Triggers on: is it done, ready to commit, verify correctness, did I miss anything, pre-commit check.

Skill: aposd-verifying-correctness

STOP - Before "Done"

Design quality ≠ correctness. Well-designed code can still have bugs, missing requirements, or safety issues.

Run ALL dimension checks before claiming done. "I think I covered everything" without explicit mapping is a red flag.

---

Dimension Detection & Checks

For each dimension: detect if it applies, then verify.

---

1. Requirements Coverage

Detect: Were requirements stated? (explicit list, user request, spec)

If YES, verify:

• List each requirement explicitly
• For each: point to code that implements it
• Any requirement without code? → Not done
• Any code without requirement? → Scope creep or missing requirement

Red flag: "I think I covered everything" without explicit mapping

---

2. Concurrency Safety

Detect: Any of these present?

• Multiple threads/processes accessing same data
• Async/await patterns
• Shared mutable state (class attributes, globals)
• "Thread-safe" in requirements or docstring