test

Run acceptance tests against implemented code and present pass/fail results.

36|3|Updated Apr 6, 2026
One-click install
npx skills add https://github.com/dfrysinger/qrspi-plus --skill test-dfrysinger
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test
Source: https://github.com/dfrysinger/qrspi-plus/tree/main/skills/test
Command: npx skills add https://github.com/dfrysinger/qrspi-plus --skill test-dfrysinger

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Test skill verifies that an implementation satisfies the original goals by running focused acceptance, integration, E2E, and boundary tests, presenting deterministic pass/fail results, and coordinating fix dispatch without making production code changes.

Core Features & Use Cases

  • Acceptance coverage: Maps each goals.md acceptance criterion to one or more explicit tests and produces a coverage analysis for user approval.
  • Test orchestration and gating: Runs existing suites, reviews test code (Pattern 1), executes approved tests once deterministically, and presents detailed pass/fail artifacts to the human gate.
  • Fix routing and PR handling: Classifies failures as quick or full pipeline fixes, writes fix task files, routes fixes through the appropriate subagents, and prepares PRs after approval.

Quick Start

Run the Test skill to execute approved acceptance tests, present coverage and results, and dispatch fix tasks or prepare the phase PR as instructed.

Frequently Asked Questions about test

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

FAQPage Schema
How do I run acceptance tests to verify my implementation meets original goals?

Acceptance tests verify your implementation by mapping each goals.md criterion to explicit tests, executing the approved suite deterministically, and presenting pass/fail artifacts for human review before proceeding.

How do I route failing test cases into fix tasks without touching production code?

Failing test cases are routed by classifying them as quick or full pipeline fixes, writing fix task files, and dispatching them through appropriate subagents, all while the test skill maintains constrained authority to never change production code.

What do I need to set up before executing test orchestration and coverage analysis?

Test orchestration requires approved goals.md and design.md or research/summary.md files, access to the codebase and fixes history, and deterministic test execution to map acceptance criteria and produce coverage analysis for approval.

Can I automate PR creation after my acceptance test suite passes?

PR creation requires explicit user confirmation after the acceptance test suite passes and results are presented, ensuring the human gate approves the pull request preparation before any code merge proceeds.

What is the best way to map acceptance criteria to boundary and integration tests?

Mapping acceptance criteria involves running focused acceptance, integration, E2E, and boundary tests against implemented code to verify original goals, producing a detailed coverage analysis for user approval.

Why does test execution need to be deterministic when reviewing test code?

Deterministic test execution ensures approved tests run once to produce stable, repeatable pass/fail artifacts, enabling accurate fix routing and reliable human gating without flaky test interference.