Validator Agent Pattern

Cross-check implementations against PRD requirements and generate validation reports.

Updated Dec 18, 2025
One-click install
npx skills add https://github.com/multicam/trading-views --skill validator-agent-pattern
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Validator Agent Pattern
Source: https://github.com/multicam/trading-views/tree/main/.claude/skills/validator-agent
Command: npx skills add https://github.com/multicam/trading-views --skill validator-agent-pattern

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Validator Agent Pattern provides a structured approach to verify that implementations meet original PRD requirements, capture quality signals, and close feedback loops with actionable improvements.

Core Features & Use Cases

  • Requirements verification: Cross-check PRD criteria against implemented features and tests.
  • Quality testing & feedback: Run unit/integration/E2E tests, collect stakeholder feedback, and document issues.
  • Actionable validation outputs: Generate validation reports and create new work orders to drive PRD refinements and deployment readiness.

Quick Start

To begin validating a completed feature, load the PRD, load the implementation, run tests, collect feedback, and generate a validation report that highlights gaps and recommended follow-up actions.

Frequently Asked Questions about Validator Agent Pattern

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

FAQPage Schema
How do I validate that an implementation meets the original PRD requirements?

Validation cross-checks PRD criteria against implemented features and test results to confirm requirements are met. Load the PRD and implementation, run unit, integration, and end-to-end tests, collect stakeholder feedback, then generate a validation report that documents gaps and confirms coverage against the original specification.

What's the best way to structure a validation report after testing?

A validation report aggregates test results, requirement verification outcomes, and user feedback into a formal document that identifies gaps and generates actionable work orders. This structured output guides PRD refinements and deployment readiness by making issues and follow-up actions explicit.

Can I automate validation across unit, integration, and end-to-end tests?

Yes. Automated verification runs test suites at multiple levels—unit, integration, and end-to-end—to gather quality signals consistently. The validation process then aggregates these results and surfaces issues for triage, reducing manual effort while ensuring comprehensive coverage.

How do I close feedback loops between QA and development?

Validation generates work orders from test failures, stakeholder feedback, and requirement gaps, creating explicit follow-up actions that feed back into PRD updates and implementation cycles. This structures the feedback loop so issues drive concrete refinements rather than remaining unaddressed.

What should I do if validation surfaces unmet requirements before deployment?

The validation report prioritizes gaps and issues as work orders, allowing you to decide whether to refine the implementation, update the PRD, or defer features before deployment. This prevents shipping implementations that diverge from original intent.