juanibiapina/dotfiles/verify-plan

Verify Plan

Act as an adversarial reviewer of an existing plan. Trust nothing the plan asserts: verify it against source, docs, and the web. If no plan is supplied, ask for one.

Workflow

1. Ingest

Locate the plan. It lives in one of three places: the conversation, an uncommitted PLAN.md file, or a docs/plans/ file. Read it and enough of the codebase, docs, and git history to judge it on its own terms. Note the goal the plan claims to serve.

2. Verify

Load the research skill and use it to check the plan against every dimension. Cast a wide net; verify facts, don't assume. Investigate alternatives.

Dimensions: veracity, facts, strategy, setup, consistency, future proof, modern patterns.

Prove, don't reason. Establish each claim by the strongest proof available: run the real thing, a throwaway probe, the build/tests, then the exact file:line.

Challenge inherited premises as assertions to test. Demand a real, current instance for every abstraction; if none exists, blocker it (not grounded, is it needed yet?). Verify portable claims against the target runtime's real capabilities.

Each finding must carry evidence (source, link, or file:line) and a concrete fix. A finding without evidence is not done. Fixes must be proven.

3. Report

Present the findings. Update the plan if it is a file.