What problem does it solve? A definition-of-done checklist is only an assertion until someone proves it. This Skill turns each task's definition of done into a structured verification protocol — a done certificate — that names exactly what evidence a validator must collect and which checks to run, so completion is proven rather than assumed. ## Core Features & Use Cases - Certificate authoring: Converts each definition-of-done item into a proof obligation with a claim, precise evidence-to-collect instructions, and function-resolution or regression checks, leaving status and verdict blank for a validator. - spec-planner integration: Writes one certificate per task co-located beside its task file in a spec-planner plan, with two-way links and append-only numbering that moves through backlog, in-progress, and done folders. - Standalone use: Works over any task with acceptance criteria — tickets, PRDs, or issue checklists — writing certificates to .specs/certificates/ when no plan exists. - Use Case: After spec-planner produces a six-task plan for a journal app, ask for done certificates and receive six unverified verification protocols, each naming the exact tests, file locations, and execution traces a validating agent must run to declare the task done. ## Quick Start Ask the agent to add done certificates to each task in your spec-planner plan, or to create a done certificate from a ticket's acceptance criteria.
