Назад към всички

verification

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

$ git log --oneline --stat
stars:384
forks:73
updated:March 4, 2026
SKILL.mdreadonly
SKILL.md Frontmatter
nameverification
descriptionVerification-before-completion discipline ensuring all success criteria are met, tests pass, and reviews complete before declaring work done.
allowed-toolsRead, Bash, Grep, Glob, Agent, AskUserQuestion

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)