Plan, execute, and document QA test cycles with structured inputs and summaries.
npx skills add https://github.com/qa-aman/claude-skills --skill qa-execution
Please help me install this Agent Skill. Skill: qa-execution Source: https://github.com/qa-aman/claude-skills/tree/main/skills/by-role/qa/qa-execution Command: npx skills add https://github.com/qa-aman/claude-skills --skill qa-execution
QA teams struggle to organize, execute, and document test work across smoke, regression, and exploratory cycles. This skill provides a structured approach to plan, perform, and record testing activities to improve release readiness.
Trigger a test cycle by describing the build, scope, and charter, then capture and share the results.
High-intent search queries and answers about installing and using this skill.
To structure a QA test cycle for release readiness, define the test type, build, scope, and charter. This structured approach enforces necessary inputs to plan, perform, and record testing activities across smoke, regression, and exploratory sessions.
The best way to document exploratory testing is by capturing the test charter, scope, and outcomes within a structured QA cycle. This approach records what was tested, by whom, and when, producing shareable summaries and defect-ready evidence.
You can capture and share QA test results by running a structured test cycle that generates a succinct test run summary. This provides traceability for releases and documents outcomes to improve accountability across the testing team.
Yes, you can use this for both smoke tests and regression suites. The skill applies across smoke, regression, and exploratory cycles, enforcing structured inputs like test type and build to capture full results and improve release readiness.
No specific test frameworks are required to plan a test cycle. You trigger a cycle by describing the build, scope, and charter, allowing the skill to organize and document the testing activities without external framework dependencies.
QA testing lacks traceability when cycles are not structured with defined inputs. By planning test cycles with specific build and scope parameters, you produce traceable test run summaries and defect-ready evidence to verify release readiness.
AZANIRDesign manual test cases and exploratory testing charters using specification-based techniques.
augustoheissAnalyze raw test results to identify failure patterns, coverage gaps, and release readiness.
jammindevReproduce software bugs, add failing regression tests, and verify fixes.
jamesrochabrunGenerate QA test plans, manual cases, regression suites, and bug reports.
