superpowers-verification-before-completion

Run defined verification commands and cite output before declaring work complete.

Updated Apr 23, 2026

Search Tags:#verification #completion #evidence #code-review #pull-request

Ready to run

npx skills add https://github.com/qq824045252-ship-it/erp --skill superpowers-verification-before-completion-qq824045252-ship-it

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: superpowers-verification-before-completion
Source: https://github.com/qq824045252-ship-it/erp/tree/main/.agents/skills/superpowers-verification-before-completion
Command: npx skills add https://github.com/qq824045252-ship-it/erp --skill superpowers-verification-before-completion-qq824045252-ship-it

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill ensures you don't claim work as complete without running verification commands and collecting fresh evidence, preventing false positives.

Core Features & Use Cases

Enforces a structured verification workflow before status updates or PRs.
Provides a repeatable process to run verification commands, review outputs, and cite evidence.
Suitable for teams enforcing honesty and quality gates before releasing changes, merging PRs, or reporting completion status.

Quick Start

Run the defined verification command suite and report the results before declaring completion.

Frequently Asked Questions about superpowers-verification-before-completion

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I enforce verification before declaring a pull request complete?▼

To enforce verification before declaring a pull request complete, run a defined verification command suite, review the full output, and cite the fresh evidence to satisfy your completion claim. This prevents false positives during code reviews.

Why does claiming task completion without evidence cause issues in software development?▼

Claiming task completion without fresh evidence causes issues because it prevents false positives during task handoffs. Running verification commands and collecting actual output ensures outcomes are backed by proof rather than assumptions.

What is the best way to structure a code review workflow to prevent false completions?▼

The best way to structure a code review workflow to prevent false completions is enforcing a repeatable process where developers run verification commands, review outputs, and cite evidence before reporting completion status or merging changes.

Can I use this structured verification workflow for task handoffs?▼

Yes, you can use this structured verification workflow for task handoffs. It ensures developers collect and provide fresh evidence by running defined verification commands before reporting completion status to the receiving team.

Does this verification process work without configuring external dependencies?▼

Yes, the verification process works without external dependencies, but it requires a defined verification command suite to exist. You must run these commands and review their full output to cite results for completion claims.