What problem does it solve? A zero exit status only proves a process terminated normally, not that the intended handler actually ran. This Skill closes that gap when implementation plans specify exact CLI, module, migration, or validation commands whose success depends on observable output or state changes. ## Core Features & Use Cases - Exact-Command Verification: Runs the literal command from the plan in the specified directory and environment, never substituting a unit-level function call. - Evidence-Based Assertions: Declares required evidence before execution (stdout/stderr, created artifacts, database state, exit code) and adds subprocess-level tests asserting it. - No-Op Detection: Treats exit zero with missing output or missing state change as a failed verification, investigating entrypoints like main, argument dispatch, and early returns. - Use Case: A plan requires running a database migration command. The command exits 0 but no migration applied because of a broken argument dispatch. This Skill catches the no-op by asserting the declared database state change. ## Quick Start Use executing-plans-extras to verify that each CLI command in my implementation plan actually produced its declared evidence before marking the task complete.
