verification-before-completion
Verification Before Completion
[2026-02-01 CONSOLIDATION NOTE] This is the OBRA version (
obra-verification-before-completion), which was promoted as the primary implementation due to:
- More structured Copilot Completion Checklist (Requirements/Correctness/Quality/Verification)
- Explicit "Why This Matters" context from failure memories
- Agent delegation pattern guidance
Overview
Claiming work is complete without verification is dishonesty, not efficiency.
Core principle: Evidence before claims, always.
Violating the letter of this rule is violating the spirit of this rule.
Copilot Completion Checklist
More from faulkdev/github-copilot-superpowers
minimalist-surgical-development
Use when editing an existing codebase and the goal is minimal, standard, and non-invasive changes - prioritizes simplest solution, standard libraries first, and surgical modification without unsolicited refactors
34uncertainty-verification
Use when providing exact commands, flags, config keys, file paths, API details, standards, or version-specific behavior - enforces verification via official docs (Context7/web fetch), explicit citations, and bans assumption-based specifics
20investigation-mode
DEPRECATED: See systematic-debugging for current implementation.
14root-cause-tracing
Use when errors occur deep in execution and you need to trace back to find the original trigger - systematically traces bugs backward through call stack, adding instrumentation when needed, to identify source of invalid data or incorrect behavior
13task-direction-approval
Use when considering switching libraries/tools, changing architecture, or replacing automation with manual workarounds - explains root cause, offers 2-3 options with trade-offs, and requests explicit user choice
13systematic-debugging
Use when errors are unclear, flaky, or regressions occur; apply a disciplined debugging loop in VS Code Copilot Agent mode.
3