skills.rest
xhyqaq
xhyqaqCOMMUNITY
Explore all skills by this author →
GitHub

acceptance-testing

Verify completed feature branches against predefined acceptance criteria before merging.

63|2|Updated Mar 29, 2026
Search Tags:#code review#development workflow#quality gate#subagent#test verification#acceptance testing#branch merging
One-click install
npx skills add https://github.com/xhyqaq/superpowers-plus --skill acceptance-testing-xhyqaq
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: acceptance-testing
Source: https://github.com/xhyqaq/superpowers-plus/tree/main/skills/acceptance-testing
Command: npx skills add https://github.com/xhyqaq/superpowers-plus --skill acceptance-testing-xhyqaq

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the risk of merging incomplete or non-compliant feature branches that fail to meet user-approved requirements, which can lead to costly post-deployment rework and broken user experiences.

Core Features & Use Cases

  • Automated Criterion Verification: Dispatches a dedicated acceptance tester subagent to run tests for every predefined acceptance criterion, removing manual verification gaps.
  • Dependency-Aware Testing: Automatically blocks testing of dependent criteria if their prerequisites fail, avoiding invalid test results.
  • Workflow Integration: Fits seamlessly into standard development workflows, running after code review is complete and before branch finishing to enforce quality gates.
  • Use Case: After building a new user authentication feature, use this Skill to confirm all acceptance criteria (e.g., password reset functionality, 2FA enrollment) pass before merging to the main branch.

Quick Start

Use the acceptance-testing skill to verify the current feature branch satisfies all approved acceptance criteria before merging it to the main codebase.

Frequently Asked Questions about acceptance-testing

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

FAQPage Schema
How do I verify acceptance criteria before merging a feature branch?▼

Dependency-aware acceptance testing automatically blocks testing of dependent criteria if their prerequisites fail. This prevents invalid test results and ensures prerequisite failures halt downstream verification, enforcing strict quality gates before merging branches.

When do I need automated acceptance testing in my development workflow?▼

Automated acceptance testing is needed after code review is complete and before branch finishing. It fits into standard development workflows to confirm completed software implementation branches fully satisfy predefined acceptance criteria before integrating into the main codebase.

Can I use this acceptance testing skill with my existing branch finishing workflow?▼

Yes, this Skill coordinates with existing plan execution and branch finishing workflows. It applies to post-code-review development workflows to block merging of incomplete features, fitting seamlessly into your standard development pipeline as a quality gate.

What is the best way to automate criterion-specific tests for a new feature?▼

The best way to automate criterion-specific tests is dispatching a dedicated acceptance tester subagent for every predefined acceptance criterion. This removes manual verification gaps and generates formal pass/fail reports to enforce merge gating.

Why does dependency-aware testing block certain acceptance criteria from running?▼

Dependency-aware testing blocks dependent criteria if their prerequisites fail to avoid invalid test results. By automatically halting testing of interdependent criteria, it ensures prerequisite failures invalidate downstream verification and prevent merging non-compliant features.

Related Skills

Explore More Software Engineering Skills→
haidonglethqbhaidonglethqb

code-review

Define code-review scope and trigger verification steps across impacted files.

Community
Advanced
miles990miles990

finishing-a-development-branch

Present four merge, PR, keep, or discard options after tests pass.

Community
Intermediate
nth5693nth5693
370

code-review

Automate multi-perspective code reviews with structured checklists and workflow prompts.

Community
Basic
kekemotokekemoto

harness-coder

Automate sequential spec implementation with acceptance criteria, testing, and commits in a feature branch.

Community
Advanced