verification-before-completion
Skill1 starsChanged 6 months agoMITView on GitHub
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
189 other projects use a version of this.
Adopted by
Most recently taken up by
- DemonDamon/AgenticXtheir own version, first seen Nov 9, 2026
- roundpilot/superpowers-antigravitytheir own version, first seen Nov 8, 2026
- REPOZY/superpowers-optimizedtheir own version, first seen Nov 8, 2026
- lingyired/status-triotheir own version, first seen Nov 8, 2026
- DJtx001/ai-coding-playbooktheir own version, first seen Nov 8, 2026
- Ai-assistant-KIRA/antigravity-harnesstheir own version, first seen Nov 8, 2026
Used with
Projects with it also use chinese-code-review, chinese-commit-conventions and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
Leodorareluctant259Skillchinese-code-review
中文代码审查规范——在保持专业严谨的同时,用符合国内团队文化的方式给出有效反馈
Also in 8 projects that use this
Leodorareluctant259Skillchinese-commit-conventions
中文 Git 提交规范 — 适配国内团队的 commit message 规范和 changelog 自动化
Also in 8 projects that use this
obraSkilldiagnosing-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 long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.
Also in 20 projects that use this
jh941213Skilldocs-ci
문서 CI(링크·OpenAPI lint·breaking 게이트·mermaid 검증)나 문서 드리프트 감지(docs.yaml 신선도 검사)를 설치하거나 돌릴 때 사용. 문서 내용 작성은 docs-architecture·docs-interfaces·docs-manuals.
Also in 3 projects that use this
jh941213Skilldocs-interfaces
API·이벤트 인터페이스 문서(OpenAPI·swagger·AsyncAPI 명세, 엔드포인트 레퍼런스, API 구성도·시퀀스, API CHANGELOG)를 만들거나 코드와 맞출 때 사용. 시스템 구성도는 docs-architecture, API 설계 원칙은 api-design-principles.
Also in 3 projects that use this
- +3 more from Leodorareluctant259
- +4 more from jh941213
Other versions189 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 189
- obra/superpowers★ 314ksame name
- jnMetaCode/superpowers-zh★ 8.4ksame name
- openai/plugins★ 7.8ksame name
- farm-fe/farm★ 5.6ksame name
- lingyired/status-trio★ 1.8ksame name
- GanyuanRan/Aegis★ 1.4ksame name
- pcvelz/superpowers★ 1.3ksame name
- DemonDamon/AgenticX★ 1ksame name
- coco-research/coco★ 797same name
- pedronauck/skills★ 649same name
179 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository20 other files it gives its agents.
- finishing-a-development-branchSkill
- receiving-code-reviewSkill
- requesting-code-reviewSkill
- systematic-debuggingSkill
- api-designSkill
- database-migrationsSkill
- fastapi-patternsSkill
- logging-standardsSkill
- python-patternsSkill
- redis-patternsSkill
- springboot-patternsSkill
- security-reviewSkill
- using-superpowersSkill
- java-testingSkill
- python-testingSkill
- test-driven-developmentSkill
- brainstormingSkill
- executing-plansSkill
- subagent-driven-developmentSkill
- writing-plansSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
14 rules. 0 are common, 11 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 177 edited versions we read keep these.
11
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 25
Before any success/completion statement:
- Distinctive: line 28
Run full command(s) now.
- Distinctive: line 29
Read full output and exit code.
- Distinctive: line 43
If known mistakes repeated without prevention checks, stop and fix process first.
- Distinctive: line 52
Before completion claim, verify from plan artifacts:
- Distinctive: line 63
Run coverage report and confirm thresholds are met:
- Distinctive: line 74
If coverage is below threshold, add missing tests before claiming completion.
- Very specific: line 82
No open blocking mistakes in 99-mistake-log.md
- Very specific: line 83
No open CR-### or DR-### in 05-change-log.md
- Distinctive: line 87
Before completing the Minimum Checklist, confirm the evidence matches the task type:
- Very specific: line 90
Test run stdout: all tests passed (BUILD SUCCESSFUL, Tests run: N, Failures: 0, Errors: 0)
- Distinctive: line 94
If the task adds or modifies an API endpoint: include an actual HTTP request + response (status code + body)
- Distinctive: line 104
If multi-environment: list which environments the change has been applied to
- Distinctive: line 135
Run commands. Read outputs.
“Common” is measured: kept by at least 6 in 10 of the 177 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Verification Before Completion
Prerequisites
| From skill | Must already exist | If missing |
executing-plans | All tasks in 03-implementation-plan.md marked completed | Return to executing-plans — verification cannot start with open tasks |
executing-plans | 04-verification.md updated with evidence for each completed task | Return to executing-plans to fill evidence before running gates here |
Overview
Claims require evidence. No completion claim is valid without fresh verification outputs.
The Iron Law
NO COMPLETION CLAIMS WITHOUT FRESH VERIFICATION EVIDENCE
Command Evidence Gate
Before any success/completion statement:
- Identify command(s) that prove the claim.
- Run full command(s) now.
- Read full output and exit code.
- State result with evidence only.
Mistake Recurrence Gate
Review:
docs/plans/YYYY-MM-DD-<feature-name>/99-mistake-log.mddocs/memory/global-mistakes.md
Research Recheck Gate
If 06-research-notes.md exists:
If known mistakes repeated without prevention checks, stop and fix process first.
- Recheck all entries marked
Recheck Needed. - Record recheck result in
04-verification.md.
Completion claims are invalid while required rechecks are pending.
Requirement Closure Gate (MANDATORY)
Before completion claim, verify from plan artifacts:
unmapped_req = 0(all activeREQ-###mapped to plan tasks and verification items)open_cr = 0(allCR-###closed or explicitly deferred with approval)open_dr = 0(allDR-###closed or explicitly deferred with approval)pending_recheck = 0(research rechecks done)
Record these values in 04-verification.md.
Coverage Gate
Run coverage report and confirm thresholds are met:
| Layer | Minimum |
| Service (business logic) | 85% |
| Controller | 80% |
| Overall project | 80% |
Commands:
- Java:
./gradlew test jacocoTestReport→ checkbuild/reports/jacoco/
If coverage is below threshold, add missing tests before claiming completion.
Minimum Checklist
- Tests/build/lint evidence attached
- Coverage thresholds met (evidence from report)
- Requirement checklist verified line-by-line
04-verification.mdupdated- No open blocking mistakes in
99-mistake-log.md - No open
CR-###orDR-###in05-change-log.md
Evidence Templates by Task Type
Before completing the Minimum Checklist, confirm the evidence matches the task type:
code-task
- Test run stdout: all tests passed (
BUILD SUCCESSFUL,Tests run: N, Failures: 0, Errors: 0) - JaCoCo coverage summary: Service ≥ 85%, Controller ≥ 80%, Overall ≥ 80%
- Command:
./gradlew test jacocoTestReport - Report:
build/reports/jacoco/test/html/index.html
- Command:
- If the task adds or modifies an API endpoint: include an actual HTTP request + response (status code + body)
migration-task
- Flyway run log:
Successfully applied N migration(s) to schema - Schema state after migration: output of
DESCRIBE <table>orSHOW CREATE TABLE <table>showing expected columns and indexes - Rollback test: run rollback migration and confirm schema returns to pre-migration state (show output)
config-task
- Application startup log showing configuration loaded without errors
- Functional smoke test output confirming the affected behavior works
- If multi-environment: list which environments the change has been applied to
api-endpoint (supplement to code-task)
Provide all three:
# Success path
Request: POST /api/xxx
Body: {"field": "value"}
Response: HTTP 200 {"code": 0, "data": {...}}
# Error path
Request: POST /api/xxx
Body: {"field": ""}
Response: HTTP 400 {"code": "INVALID_PARAM", "message": "..."}
# Auth rejection (if endpoint is protected)
Request: POST /api/xxx (no token)
Response: HTTP 401"It should work" or "tests cover this" is not evidence. Paste actual output.
Red Flags
- "Should pass now"
- "Looks good" without running commands
- Declaring done while requirement mapping is incomplete
- Delegated agent said success but no independent verification
Bottom Line
Run commands. Read outputs. Verify requirement closure. Then claim completion.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

