validate

Name: validate
Availability: InStock
Author: jayprimer

Validate recorded test trajectories against actual execution and script coverage.

Updated Jan 4, 2026

Search Tags:#qa #audit #evidence #coverage #test #trajectory #validate

Ready to run

npx skills add https://github.com/jayprimer/pmc-marketplace --skill validate-jayprimer

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: validate
Source: https://github.com/jayprimer/pmc-marketplace/tree/main/plugins/pmc/skills/validate
Command: npx skills add https://github.com/jayprimer/pmc-marketplace --skill validate-jayprimer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validate test execution against recorded trajectories and confirm script coverage for all defined test cases, providing an auditable integrity trail.

Core Features & Use Cases

Trajectory validation: compare recorded steps to actual actions and verify RED/GREEN markers.
Evidence and coverage: ensure artifacts exist and coverage aligns with 3-spec.md.
Audit readiness: support reviews of others' work and pre-ticket completion.

Quick Start

Run a full trajectory validation cycle against the current ticket suite to produce a validation report.

Frequently Asked Questions about validate

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

FAQPage Schema

How do I validate recorded test trajectories against actual execution?▼

Test trajectory validation compares recorded steps to actual actions and verifies RED/GREEN markers to identify discrepancies. It requires access to tests.json and trajectory logs to confirm execution integrity across unit and integration tests.

What is script coverage verification for defined test cases?▼

Script coverage verification ensures artifacts exist and coverage aligns with 3-spec.md. It confirms all defined test cases are executed and produces an auditable integrity trail for post-test audits and peer reviews.

Do I need tests.json and trajectory logs to run a validation cycle?▼

Yes, validation requires access to tests.json, 3-spec.md, and trajectory logs. These files provide the test cases, specifications, and recorded execution data needed to compare trajectories and verify coverage.

Can I use trajectory validation for pre-ticket completion checks?▼

Yes, trajectory validation supports pre-ticket completion by verifying script coverage and execution integrity. It runs full validation cycles against ticket suites to produce reports confirming all test cases pass and evidence exists.

What's the best way to audit test execution and verify coverage across unit and integration tests?▼

Run a full trajectory validation cycle against the current ticket suite to produce a validation report. This compares recorded steps to actual actions, verifies evidence presence, and confirms coverage alignment with specifications.

What modes are available for test trajectory validation?▼

Validation supports Quick, Full, and Coverage modes. Each mode validates trajectory structure, evidence presence, and test coverage against defined cases, allowing flexible depth for post-test audits and peer reviews.