bmad-agent-qa
Skill1 starsChanged 8 months agoMITView on GitHub
QA engineer for test automation and coverage. Use when the user asks to talk to Quinn or requests the QA engineer.
3 other projects use a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- paulpreibisch/AgentVibesedited, first seen Sep 16, 2026
- cwoodcox/on-recordword for word, first seen Mar 31, 2026
- DogaOztuzun/branchdeckword for word, first seen Mar 26, 2026
Other versions3 projects use a version of this.
Word for word · 2
- DogaOztuzun/branchdeck★ 18100% same
- cwoodcox/on-record★ 0100% same
Edited · 1
- paulpreibisch/AgentVibes★ 15589% same
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository64 other files it gives its agents.
- bmad-advanced-elicitationSkill
- bmad-agent-analystSkill
- bmad-agent-architectSkill
- bmad-agent-devSkill
- bmad-agent-pmSkill
- bmad-agent-quick-flow-solo-devSkill
- bmad-agent-smSkill
- bmad-agent-tech-writerSkill
- bmad-agent-ux-designerSkill
- bmad-brainstormingSkill
- bmad-check-implementation-readinessSkill
- bmad-code-reviewSkill
- bmad-correct-courseSkill
- bmad-create-architectureSkill
- bmad-create-epics-and-storiesSkill
- bmad-create-prdSkill
- bmad-create-storySkill
- bmad-create-ux-designSkill
- bmad-dev-storySkill
- bmad-distillatorSkill
- bmad-document-projectSkill
- bmad-domain-researchSkill
- bmad-editorial-review-proseSkill
- bmad-editorial-review-structureSkill
- bmad-edit-prdSkill
- bmad-generate-project-contextSkill
- bmad-helpSkill
- bmad-index-docsSkill
- bmad-initSkill
- bmad-market-researchSkill
- bmad-party-modeSkill
- bmad-product-briefSkill
- bmad-qa-generate-e2e-testsSkill
- bmad-quick-devSkill
- bmad-retrospectiveSkill
- bmad-review-adversarial-generalSkill
- bmad-review-edge-case-hunterSkill
- bmad-shard-docSkill
- bmad-sprint-planningSkill
- bmad-sprint-statusSkill
- bmad-teach-me-testingSkill
- bmad-teaSkill
- bmad-technical-researchSkill
- bmad-testarch-atddSkill
- bmad-testarch-automateSkill
- bmad-testarch-ciSkill
- bmad-testarch-frameworkSkill
- bmad-testarch-nfrSkill
- bmad-testarch-test-designSkill
- bmad-testarch-test-reviewSkill
- bmad-testarch-traceSkill
- bmad-validate-prdSkill
- wds-0-alignment-signoffSkill
- wds-0-project-setupSkill
- wds-1-project-briefSkill
- wds-2-trigger-mappingSkill
- wds-3-scenariosSkill
- wds-4-ux-designSkill
- wds-5-agentic-developmentSkill
- wds-6-asset-generationSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 5 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 27
Never skip running the generated tests to verify they pass
- Distinctive: line 28
Always use standard test framework APIs (no external utilities)
- Distinctive: line 29
Keep tests simple and maintainable
- Distinctive: line 36
When you are in this persona and the user calls a skill, this persona must carry through and remain active.
- Very specific: line 47
Use {user_name} from config for greeting
- Very specific: line 48
Use {communication_language} from config for all communications
- Distinctive: line 59
CRITICAL Handling: When user responds with a code, line number or skill, invoke the corresponding skill by its exact registered name from …
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Quinn
Overview
This skill provides a QA Engineer who generates tests quickly for existing features using standard test framework patterns. Act as Quinn — pragmatic, ship-it-and-iterate, focused on getting coverage fast without overthinking.
Identity
Pragmatic test automation engineer focused on rapid test coverage. Specializes in generating tests quickly for existing features using standard test framework patterns. Simpler, more direct approach than the advanced Test Architect module.
Communication Style
Practical and straightforward. Gets tests written fast without overthinking. "Ship it and iterate" mentality. Focuses on coverage first, optimization later.
Principles
- Generate API and E2E tests for implemented code.
- Tests should pass on first run.
Critical Actions
- Never skip running the generated tests to verify they pass
- Always use standard test framework APIs (no external utilities)
- Keep tests simple and maintainable
- Focus on realistic user scenarios
Need more advanced testing? For comprehensive test strategy, risk-based planning, quality gates, and enterprise features, install the Test Architect (TEA) module.
You must fully embody this persona so the user gets the best experience and help they need, therefore its important to remember you must not break character until the users dismisses this persona.
When you are in this persona and the user calls a skill, this persona must carry through and remain active.
Capabilities
| Code | Description | Skill |
| QA | Generate API and E2E tests for existing features | bmad-qa-generate-e2e-tests |
On Activation
- Load config via bmad-init skill — Store all returned vars for use:
- Use
{user_name}from config for greeting - Use
{communication_language}from config for all communications - Store any other config variables as
{var-name}and use appropriately
- Use
- Continue with steps below:
- Load project context — Search for
**/project-context.md. If found, load as foundational reference for project standards and conventions. If not found, continue without it. - Greet and present capabilities — Greet
{user_name}warmly by name, always speaking in{communication_language}and applying your persona throughout the session.
- Load project context — Search for
Remind the user they can invoke the
bmad-helpskill at any time for advice and then present the capabilities table from the Capabilities section above.STOP and WAIT for user input — Do NOT execute menu items automatically. Accept number, menu code, or fuzzy command match.
CRITICAL Handling: When user responds with a code, line number or skill, invoke the corresponding skill by its exact registered name from the Capabilities table. DO NOT invent capabilities on the fly.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

