verifying

Run full test suites and cross-check requirements.md and plan.md for completion eligibility.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/astrosteveo/epic --skill verifying
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verifying
Source: https://github.com/astrosteveo/epic/tree/main/plugins/harness/skills/verifying
Command: npx skills add https://github.com/astrosteveo/epic --skill verifying

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Rigorous validation ensures that execution truly meets requirements and user expectations before marking work complete.

Core Features & Use Cases

  • Full Validation: Runs complete test suites and requirement checks.
  • Plan Alignment: Verifies each plan step was executed as intended.
  • Peer Review: Delegates to verifier agent for independent assessment.

Quick Start

After execution, run the verification flow to confirm tests pass and requirements are satisfied; obtain user satisfaction confirmation.

Frequently Asked Questions about verifying

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify that my code changes pass all tests before completing work?

Verification runs your complete test suite and validates requirements to confirm changes meet specifications. Execute the full validation flow after code changes to check test results and requirement alignment before marking work complete.

What's the best way to ensure my implementation matches the plan and requirements?

Validation cross-checks your plan.md and requirements.md against executed work step-by-step. The verification process confirms each planned action was completed as intended and all requirements are satisfied.

Can I get peer review feedback integrated into my quality assurance process?

Yes. Verification includes a peer-review gate that delegates independent assessment to a verifier agent, providing external validation before sign-off alongside automated test results.

When should I run validation in my development workflow?

Run verification after execution or code changes, before sign-off, and whenever validation is requested. It acts as a completion eligibility gate by testing requirements satisfaction and user expectations.

Does verification require specific test framework setup?

Verification executes your existing full test suite without framework dependency. It works with any testing approach as long as tests are runnable; setup depends on your project's test infrastructure.

What happens if requirements or plan validation fails?

Validation identifies misalignment between execution and requirements.md or plan.md before completion. Failures flag work not yet ready for sign-off, allowing correction before user satisfaction confirmation.