writing-verification-plans

Define each real-world scenario with its starting context, step-by-step actions, and observable success criteria, then record them in a VERIFICATION_PLAN.md. This Skill gathers that information through questions and generates the plan in a standard format.

A verification plan uses real running systems and never mocks or fakes, producing manual or agent-executed acceptance procedures. Integration tests are automated code suites; this Skill explicitly does not write unit or integration test code.

No. The core rule is that verification must prove real-world behavior, so mocks and fakes are never allowed. A test environment is acceptable only when it is a fully running copy of the real system being integrated with.

Create one when setting up a new project, when the repository lacks a VERIFICATION_PLAN.md, or when adding features that need real-world validation. Verification then runs automatically after completing any task.

The blocker is documented exactly, execution stops, and the developer is asked for help rather than guessing or skipping scenarios. The task is not marked complete until verification passes.