BrainstormingTop pick
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it…
Coding Workflow
Jesse Vincent312k
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
Install
Run this in your project folder. It works with Claude Code, Cursor, Codex and dozens of other agents.
$ npx skills add obra/superpowers --skill verification-before-completionNeeds Node.js. Add -g to install for every project, or -a claude-code to skip the agent picker.
How to use Verification Before Completion
Once it's installed, Claude reads this skill on its own whenever a request matches what it's for, so you don't have to mention it by name. In Claude Code you can also run it directly by typing /verification-before-completion.
It contains no scripts, only instructions and reference files, so it can't run code on its own.
What the instructions cover
- 1Overview
- 2The Iron Law
- 3The Gate Function
- 4Common Failures
- 5Red Flags - STOP
- 6Rationalization Prevention
- 7Key Patterns
- 8When To Apply
Section headings from the skill's SKILL.md file.
What's inside · 1 files
- SKILL.md
More from Jesse Vincent
See all →Systematic DebuggingTop pick
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Coding WorkflowJesse Vincent312k
Diagnosing Superpowers
Use when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too…
Coding WorkflowJesse Vincent312k
Dispatching Parallel Agents
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
AI & AgentsJesse Vincent312k
More Claude skills for coding
See all →CavemanTop pick
Terse caveman voice: answer first, fluff gone, every technical fact kept. Use for /caveman, "caveman mode", "talk like caveman", "be brief", "less tokens". Stays on until "stop…
Coding Workflow
Julius Brussee117k
PonytailTop pick
Lazy senior dev mode: the smallest change that fully solves the task, and a reply a busy human understands in one read. Use on any coding task (writing, fixing, refactoring…
Coding Workflow
Dietrich Gebert184k
Ponytail Audit
Quality audit of a whole repo: bugs, security holes, what breaks under real load, risky code without tests, slow paths, and what to delete, merge or split. Ranked, each finding…
Coding WorkflowDietrich Gebert184k