validation

Name: validation
Availability: InStock
Author: dhamija

Validates user promises by comparing acceptance criteria against actual outcomes.

Updated Jan 25, 2026

Search Tags:#validation #remediation #evidence #promises #acceptance-testing #feature-verification

Ready to run

npx skills add https://github.com/dhamija/claude-workflow-agents --skill validation-dhamija

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: validation
Source: https://github.com/dhamija/claude-workflow-agents/tree/main/templates/skills/validation
Command: npx skills add https://github.com/dhamija/claude-workflow-agents --skill validation-dhamija

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill ensures user promises are verified after feature completion by validating outcomes against defined acceptance criteria, reducing reliance on tests alone.

Core Features & Use Cases

Acceptance criteria extraction and validation tracking.
Manual and automated validation steps with evidence and remediation guidance.
Use Case: after implementing a feature, run validation to confirm promises are kept, producing a VALIDATED or PARTIAL/FAILED state and remediation plan.

Quick Start

Run the validation workflow on a completed feature branch to verify promises against the intent document.

Frequently Asked Questions about validation

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

FAQPage Schema

How do I validate that a feature meets its acceptance criteria after implementation?▼

Validation compares your completed feature's actual behavior against defined acceptance criteria to confirm promises are kept. Run the validation workflow on your feature branch with an intent document and evidence collection to produce a VALIDATED, PARTIAL, or FAILED state with remediation guidance.

What's the difference between validation and testing for feature verification?▼

Validation reduces reliance on tests alone by comparing expected acceptance criteria against actual outcomes across code changes, UI flows, and API behavior. It produces actionable remediation plans when discrepancies are found, complementing rather than replacing traditional testing.

What inputs does the validation workflow require?▼

Validation requires an intent document defining promises, evidence collection demonstrating actual outcomes, and a defined state framework (VALIDATED, PARTIAL, FAILED). These inputs enable comparison of expected acceptance criteria against real feature behavior.

Can I use validation for manual acceptance steps alongside automated checks?▼

Yes. Validation supports both manual and automated validation steps with evidence tracking and remediation guidance, allowing flexible verification across scenarios including code changes, UI flows, and API behavior.

When should I run validation in my development workflow?▼

Run validation after feature implementation is complete but before merging, to confirm promises are kept against acceptance criteria. It produces a remediation plan if the feature is in PARTIAL or FAILED state, guiding next steps.