openspec-sp-verify-before-complete

What problem does it solve?

Prevents premature or unsubstantiated completion claims by requiring concrete verification evidence such as passing tests, successful builds, reproduced fixes, or independent check results before reporting a task as complete.

Core Features & Use Cases

• Evidence-first completion: Mandates that assertions of completion are backed by readable verification outputs.
• Multiple verification methods: Supports test suite runs, build/compile success checks, bug reproduction and regression testing, and independent automated checks.
• Communication guardrails: Prohibits vague or performative language and prescribes precise reporting formats and checklist enforcement.
• Use Case: Use this Skill when finishing features, merging changes, closing bug tickets, or handing off work to ensure the recipient receives verifiable proof rather than assertions.

Quick Start

Before declaring a task complete, run the chosen verification method, read and record the outputs, and report the concrete evidence that supports the completion claim.