verify

Verifies a running application against PRD screen specs and acceptance criteria in a browser.

4|Updated Mar 14, 2026
One-click install
npx skills add https://github.com/VoxTechnologies/transmute-framework --skill verify-voxtechnologies
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verify
Source: https://github.com/VoxTechnologies/transmute-framework/tree/main/skills/verify
Command: npx skills add https://github.com/VoxTechnologies/transmute-framework --skill verify-voxtechnologies

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Static code analysis cannot catch runtime failures like broken routes, hydration errors, dead links, or unwired buttons. This Skill closes that gap by launching the app in a browser and verifying every screen and acceptance criterion from the PRD against the live application. ## Core Features & Use Cases - Multi-Agent Verification: Coordinates four specialized teammates covering page-by-page checks, acceptance criteria execution, AI vision screenshot review, and responsive/interaction testing. - Dynamic Scenario Generation: Builds a Feature Scenario Matrix from PRD sources and codebase analysis, covering feature flows, auth contexts, entity states, role permissions, and negative cases. - Dual Gate Decision: Produces a verification report with a PASS/CONDITIONAL PASS/FAIL gate combining percentage-based and fixability-based categorization, routing issues to remediation. - Use Case: After scaffolding and hardening a Next.js app, run Stage 6V to confirm every PRD screen loads, all acceptance criteria pass in the browser, and generate reusable Playwright regression tests. ## Quick Start Ask the agent to run visual verification of the running app against the PRD, optionally appending MODE: full, critical, or diff.

Frequently Asked Questions about verify

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

FAQPage Schema
How do I verify a running app against PRD acceptance criteria?

Run Stage 6V after the readiness report shows READY. It generates a Feature Scenario Matrix from the PRD and codebase, starts the dev server, and spawns verification teammates that execute Given/When/Then criteria in a real browser.

What is the difference between full, critical, and diff verification modes?

Full mode tests all screens and features (P0-P3) in 30-60 minutes. Critical mode covers P0/P1 features only in 15-30 minutes. Diff mode tests only screens affected by files changed since the last verified commit, and falls back to full on the first run.

Does this verification work with frameworks other than Next.js and Convex?

Yes. The examples use Playwright with Next.js and Convex, but the Skill adapts to the stack defined in plancasting/tech-stack.md, including the test directory, test runner, dev server command, and data fetching patterns.

Why does verification abort before spawning teammates?

Verification aborts if the dev server fails to start within 60 seconds or if test user login fails through the seed endpoint, auth provider CLI, and UI signup. These prerequisites block all authenticated testing, so partial verification is not attempted.

How are flaky test scenarios handled in the gate decision?

A scenario that fails once but passes on retest is marked as flaky with cause to be determined. In Stage 6V, flaky scenarios are informational and do not count toward gate failure, but in Stage 7V production verification they count as failures.