verification

Solid

Verification-before-completion discipline ensuring all success criteria are met, tests pass, and reviews complete before declaring work done.

AI & Automation 814 stars 53 forks Updated today MIT

Install

View on GitHub

Quality Score: 93/100

Stars 20%
97
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
46
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Verification Before Completion ## Overview Ensures no step or phase is declared complete without running verification. All success criteria must be met before finishing. ## When to Use - After each implementation step - At phase checkpoints - Before final completion declaration - When validating that all acceptance criteria are met ## Verification Checklist 1. All automated tests pass 2. Manual verification steps confirmed 3. Code review completed (APPROVE or APPROVE_WITH_NITS) 4. Security review passed 5. Plan document updated with completion status 6. All success criteria from the plan are satisfied 7. No untracked deviations from the plan ## Key Rules - Never declare done without running verification - Document any verification failures - Verification failures halt progress until resolved ## Tool Use Integrated into `methodologies/rpikit/rpikit-implement` (step execution and completion)

Details

Author
a5c-ai
Repository
a5c-ai/babysitter
Created
4 months ago
Last Updated
today
Language
JavaScript
License
MIT

Related Skills