qa-acceptance Skill
Produce QA acceptance criteria and a manual validation plan for a feature change — golden path, edge cases, error states, performance limits, and explicit pass/fail evidence. Published by microsoft in amplifier-app-paperclip.
What is qa-acceptance Skill?
Produce QA acceptance criteria and a manual validation plan for a feature change — golden path, edge cases, error states, performance limits, and explicit pass/fail evidence. Published by microsoft in amplifier-app-paperclip. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Testing
- Writing
- Testing use cases
- Writing use cases
Technical details
- Install or run with Copy skill directory
When to use qa-acceptance Skill
- Use it for testing.
- Use it for writing.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/amplifier-app-paperclip
- Skill file: packages/skills-catalog/catalog/bundled/quality/qa-acceptance/SKILL.md
What it does
Produce QA acceptance criteria and a manual validation plan for a feature change — golden path, edge cases, error states, performance limits, and explicit pass/fail evidence.
Skill instructions
QA Acceptance Write acceptance criteria that a reviewer can run against the running app and decide pass or fail without asking the author. The criteria are the contract — automated tests cover correctness, QA covers feature-level behavior. When to use - A feature change is heading to QA and needs a written validation plan. - A reviewer is asked to verify a PR that touches user-visible behavior. - An incident postmortem requires a regression check before reopen-prevention. - A release candidate needs a pre-cut smoke pass. When not to use - The change is unit-test-only (utility refactor, internal naming). Acceptance criteria are unnecessary churn. - You are asked to write tests against API contracts. Use contract testing, not feature QA. Acceptance criteria format Each criterion is a single, independently-verifiable statement: md - Given <starting state, when <action, then <observable outcome. Example: md - Given a CSV export with 0 rows, when the user clicks Export, then the file downlo
Explore related resources
Frequently asked questions
What is qa-acceptance?
qa-acceptance is a open-source AI agent skill with Copy skill directory. Produce QA acceptance criteria and a manual validation plan for a feature change — golden path, edge cases, error states, performance limits, and explicit pass/fail evidence.
Who is qa-acceptance best for?
qa-acceptance is best for reusing agent instructions, scripts, and references, testing workflows, writing workflows.
How do I install qa-acceptance?
Install or run qa-acceptance using Copy skill directory. Check qa-acceptance for the latest setup command.
Is qa-acceptance actively maintained?
qa-acceptance may need a closer maintenance check before production use.
