What happens if verification fails?

Progress is halted and the failure is documented; issues must be resolved before retrying verification.

Which tools support verification?

Read, Bash, Grep, Glob, Agent, and AskUserQuestion are the allowed tools used for verification.

Is verification required at every milestone?

Yes. Verification is required before declaring done at each step, at phase checkpoints, and for final completion.

verification

npx machina-cli add skill a5c-ai/babysitter/verification --openclaw

Files (1)

SKILL.md

1.1 KB

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

All automated tests pass
Manual verification steps confirmed
Code review completed (APPROVE or APPROVE_WITH_NITS)
Security review passed
Plan document updated with completion status
All success criteria from the plan are satisfied
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)

Source

git clone https://github.com/a5c-ai/babysitter/blob/main/plugins/babysitter/skills/babysit/process/methodologies/rpikit/skills/verification/SKILL.md

View on GitHub

Overview

Verification Before Completion ensures that no step is marked done until all success criteria are met. It requires automated tests to pass, manual verifications completed, and reviews approved before declaring work finished. This discipline reduces defects and keeps delivery aligned with the plan.

How This Skill Works

At each milestone, verification runs through a predefined checklist: all automated tests pass, manual verification steps are confirmed, and code reviews (APPROVE or APPROVE_WITH_NITS) and security reviews are complete. If any item fails, progress is halted and the issue is documented until resolved. The verification status gates completion within the rpikit execution flow to prevent declaring work done prematurely.

When to Use It

After each implementation step
At phase checkpoints
Before final completion declaration
When validating that all acceptance criteria are met
When updating the plan document with completion status

Quick Start

Step 1: Run all automated tests and perform required manual verifications.
Step 2: Obtain approvals from code review and security review teams.
Step 3: Update the plan with completion status and declare completion in the system.

Best Practices

Never declare done without running verification
Document any verification failures
Verification failures halt progress until resolved
Ensure all automated tests pass and manual verifications are confirmed
Complete code reviews and security reviews (APPROVE or APPROVE_WITH_NITS) before completion

Example Use Cases

A feature branch is merged only after all tests pass, manual verifications are done, code review is approved, and the completion status is updated in the plan.
A critical bug fix is not closed until regression tests pass and both code and security reviews are complete.
During a phase checkpoint, completion cannot be declared until the verification checklist is fully satisfied.
At sprint end, final status is declared only after all acceptance criteria in the plan are met and documented.
Plan document is updated with completion status after successful verification, then deployment proceeds.

Frequently Asked Questions

Add this skill to your agents