brainstorming
brainstorming
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 (a talk, a business, a renovation).
Explorar Skills
Desarrollo · SKILL.md
verification-before-completion
verification-before-completionEvidence requirement enforcement ensuring all claims are backed by logs, test results, or exit codes. Zero = success, non-zero = failure. No guessing allowed.
Independent GitHub snapshot · Automated classification · Original documentation governs
Documentación de la Skill
GitHubname: verification-before-completion description: Evidence requirement enforcement ensuring all claims are backed by logs, test results, or exit codes. Zero = success, non-zero = failure. No guessing allowed. allowed-tools: Read, Bash, Grep, Glob graph: domains: [domain:software-engineering] skillAreas: [skill-area:agentic-loops, skill-area:orchestration-loop] workflows: [workflow:feature-development] topics: [topic:developer-experience] roles: [role:tech-lead, role:backend-engineer] 2. Test output: pass/fail counts, coverage percentages 3. Logs: error messages, stack traces, resolution confirmation 4. Build output: compilation success/failure with timestamps
Rules
- Never claim "should work" without evidence
- Never claim success without exit code 0
- Never claim a bug is fixed without reproduction failure
- Always capture and report exit codes
- Always run the full test suite, not just targeted tests
- Use timeout guards (
timeout 60s) to prevent hanging
When to Use
- Before completing any BUILD workflow step
- Before claiming a DEBUG fix is verified
- Before approving a REVIEW result
- Before marking any task as done
Agents Used
integration-verifier(primary consumer)component-builder(TDD evidence)bug-investigator(fix evidence)