Plan, execute, and verify QA testing workflows with release checklists.
npx skills add https://github.com/shaul1991/shaul-plugin --skill 07-qa
Please help me install this Agent Skill. Skill: 07-qa Source: https://github.com/shaul1991/shaul-plugin/tree/main/claude-code-plugin/project-lifecycle/skills/07-qa Command: npx skills add https://github.com/shaul1991/shaul-plugin --skill 07-qa
QA and testing phase ensures software quality by establishing test strategy, checklists, and governance to reduce release risk.
Define the QA plan, secure approval, execute tests, and verify outcomes before release.
High-intent search queries and answers about installing and using this skill.
A formal QA test strategy plans, executes, and verifies testing workflows through a Plan → Review → Execute → Re-verify governance model to ensure release-ready software. It requires defining a test plan, securing explicit approval, executing tests, and verifying outcomes before release.
Checklist-driven validation in a QA workflow uses a release-checklist and acceptance criteria across development phases to enforce cross-phase alignment. This governance mechanism reduces release risk by requiring explicit user approvals at validation gates before proceeding.
Test execution plans for different Git branches are managed by storing an execution-plan.md file under a localized path like .claude/local/plans/<sanitized-branch>/07-qa/. This per-branch template structure isolates testing artifacts and maintains governance across active development streams.
Yes, this QA approach supports unit, integration, and E2E testing workflows as part of a comprehensive testing lifecycle. It enforces execution plan storage per branch and uses a release-checklist driven verification workflow to validate outcomes across all test layers.
Explicit user approvals in a software testing lifecycle are needed at governance gates between the Plan, Review, Execute, and Re-verify phases. These approval gates ensure release-ready software by preventing progression until test execution outcomes meet defined acceptance criteria.
Yes, you can use a release checklist to align QA verification across multiple development phases. It references acceptance criteria from Phases 2 through 6, providing cross-phase alignment to validate that all testing requirements are satisfied before final release.
jshsakuraDefine risk-based test scope and acceptance criteria for software releases.
DonchitosOrchestrate a multi-agent release pipeline from planning to post-release monitoring.
rajitsahaDetect and execute unit, integration, and system tests across platforms and languages.
sandgardenhqReview Go code against official style guides and static analysis guidelines.
