speckit-test

Automate user acceptance testing against GitHub issue-backed specs.

Updated Mar 30, 2026
One-click install
npx skills add https://github.com/ranvirsingh/speckit --skill speckit-test
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-test
Source: https://github.com/ranvirsingh/speckit/tree/main/skills/speckit-test
Command: npx skills add https://github.com/ranvirsingh/speckit --skill speckit-test

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

User acceptance testing against the spec. Verifies that the implementation satisfies every acceptance scenario, functional requirement, and success criterion defined in the GitHub Issue. Use this skill after implementation is complete and before retrospective — it acts as a UAT gate. Triggers on requests like "test against the spec", "verify acceptance criteria", "run UAT", or "does the implementation match the spec?"

Core Features & Use Cases

  • Orchestrates user acceptance testing against the issue-backed spec.
  • Extracts testable criteria from the GitHub Issue: acceptance scenarios, requirements, success criteria, and edge cases.
  • Guides verification strategy and organizes results for traceability.
  • Acts as a gate before e2e or retro, coordinating next steps based on outcomes.

Quick Start

Provide a GitHub issue number to start UAT and verify acceptance criteria against the spec.

Frequently Asked Questions about speckit-test

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

FAQPage Schema
How do I automate user acceptance testing against GitHub issue specs?

User acceptance testing against issue-backed specs is automated by extracting testable acceptance scenarios, requirements, and success criteria from a GitHub issue, then confirming implementation coverage. It orchestrates UAT steps and acts as a verification gate before e2e or retrospective.

What is the best way to verify acceptance criteria from a spec are met?

The best way to verify acceptance criteria is to extract testable items from the GitHub issue spec, determine a verification strategy, and confirm coverage with existing tests or code paths. It reports results for traceability to ensure implementations satisfy all defined success criteria.

When should I run UAT against issue-backed specs in my development workflow?

You should run UAT against issue-backed specs after implementation is complete and before the retrospective phase. It acts as a UAT gate that coordinates next steps based on verification outcomes, ensuring functional requirements are satisfied before project progression.

Can I use spec verification to check existing test coverage for edge cases?

Yes, spec verification extracts edge cases and testable criteria from GitHub issues to confirm coverage with existing tests or code paths. It determines the verification strategy needed to ensure all acceptance scenarios and functional requirements are fully satisfied.

Does automated UAT work without adding new test dependencies?

Automated UAT works without adding new dependencies by confirming coverage with existing tests or code paths. It orchestrates verification steps against the spec's defined acceptance scenarios and functional requirements to report results without requiring additional testing frameworks.