executing-plans
executing-plans
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available
Explore skills
Productivity · SKILL.md
verification-before-completion
verification-before-completionUse before claiming any work is complete, fixed, or passing — runs verification commands and confirms output before making success claims.
Independent GitHub snapshot · Automated classification · Original documentation governs
Skill documentation
GitHubname: verification-before-completion description: Use before claiming any work is complete, fixed, or passing — runs verification commands and confirms output before making success claims.
Verification Before Completion
Rule
Never claim "done", "fixed", or "passing" without running verification commands and showing the output.
Evidence before assertions. Always.
Checklist
Before claiming complete:
- Run the test suite: show the output
- Run the linter/formatter: show the output
- Confirm the specific behavior that was requested works
- No regressions in previously passing tests
What to Show
Tests: pytest output (N passed, 0 failed)
Lint: ruff/eslint output (clean)
Behavior: [description of manual or automated check]
If anything fails: report it honestly. Do not claim partial success as full success.