validator

Validate implementation results against planned expectations and produce evidence-based feedback.

2|1|Updated Mar 7, 2026
One-click install
npx skills add https://github.com/AutoByteus/autobyteus-agents --skill validator-autobyteus
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: validator
Source: https://github.com/AutoByteus/autobyteus-agents/tree/main/agent-teams/evidence-driven-delivery-team/agents/validator/skills/validator
Command: npx skills add https://github.com/AutoByteus/autobyteus-agents --skill validator-autobyteus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a task is implemented, someone must objectively determine whether the result actually matches the planned expectation. This Skill provides a disciplined validation workflow that compares expected versus observed behavior, records concrete evidence, and delivers a clear Pass, Fail, or Blocked verdict without drifting into re-implementation. ## Core Features & Use Cases - Expectation-to-Observation Comparison: Reads the plan expectation, acceptance conditions, and implementation result, then selects the smallest validation surface that proves the expected behavior. - Evidence Recording: Captures exact validation commands, observations, and limits so results are reproducible and auditable. - Gate-Based Validation: For experiments, records a gate disposition (Stop, Rework, Investigate, Next Gate Unlocked, Complete) so a failed prerequisite gate never unlocks a larger experiment. - Use Case: After an engineer implements a micro-task in a multi-agent delivery workflow, run this Skill to verify the result against the planner's expectation and produce a structured validation-result.md with feedback and residual risks for the planner's next-step decision. ## Quick Start Validate the latest implementation result against the planner's expectation and produce a validation-result.md using the provided template.

Frequently Asked Questions about validator

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

FAQPage Schema
How do I validate an implementation against a planned expectation?▼

Read the plan expectation, acceptance conditions, and implementation result, then select the smallest validation surface that proves the expected behavior. Execute the validation, record exact commands and observations, and classify the outcome as Pass, Fail, or Blocked.

What is gate-based validation in an experiment workflow?▼

Gate-based validation checks the cheapest sufficient surface for the current experiment gate before broader checks. It records a disposition such as Stop, Rework, Investigate, Next Gate Unlocked, or Complete, and a failed prerequisite gate never unlocks a larger experiment.

When should validation use Stop versus Investigate?▼

Use Stop when the practical hypothesis is falsified by the evidence. Use Investigate when the result may be explained by measurement error, environment issues, or route validity rather than a true failure.

What are the boundaries of a validation role?▼

Validation does not change implementation or plan artifacts, invent new expectations, or decide the entire remaining workflow. It only compares expected versus observed behavior and produces feedback the planner uses to select the next small step.

What goes into a validation-result.md file?▼

It includes the plan and task IDs, expected outcome, validation surface and commands, observed result, evidence paths, the Pass/Fail/Blocked verdict, gate disposition, feedback, residual risks, and whether the current plan can continue.