Trust But Verify

Verify that a feature implementation actually matches its plan by testing it in a real browser.

Core principle: Plans describe intent. Code describes implementation. Only the browser shows reality. This skill bridges all three — reading the plan, analyzing the diff, and verifying the result in a live browser.

When to Use

• After completing a feature branch and before merging
• When a plan exists in docs/plans/ for the current work
• When the diff touches frontend source files (UI changes)
• When you want confidence that the UI matches the spec
• When recommended by superpowers:finishing-a-development-branch

Not for: Backend-only changes, API-only work, or branches without a plan.

Process