Draft two-phase QA plans from acceptance criteria into pull request bodies.
npx skills add https://github.com/mujtaba3B/gstack-extensions --skill qa-plan-mujtaba3b
Please help me install this Agent Skill. Skill: qa-plan Source: https://github.com/mujtaba3B/gstack-extensions/tree/main/qa/skills/qa-plan Command: npx skills add https://github.com/mujtaba3B/gstack-extensions --skill qa-plan-mujtaba3b
This Skill turns a change's acceptance criteria into a structured two-phase QA plan before a pull request is reviewed or merged. It helps teams avoid vague test notes by separating merge-blocking development checks from post-deploy production checks.
Ask me to write the QA plan for the current pull request and I will turn the acceptance criteria into a two-phase QA section in the PR body.
High-intent search queries and answers about installing and using this skill.
To turn acceptance criteria into a pull request QA plan, map Given/When/Then or EARS statements into checkable QA rows. This structures validation into Development checks for local preview and Production checks for post-deploy smoke tests directly in the PR body.
A two-phase QA plan for GitHub pull requests separates merge-blocking development verification from post-deploy production verification. It translates acceptance criteria into UI flow checks, backend side effect validations, and live smoke tests to gate releases.
You automate QA section updates in a pull request body using idempotent PR-body updates. The plan writes development and production verification steps, includes a QA driver, names production artifacts, and tracks approval posture metadata.
Yes, this QA planning approach requires manual approval before merging. It presents the drafted plan for human review and only stamps approval when explicitly approved, using the QA posture metadata to gate merge and release workflows.
Yes, you can use EARS statements to generate production checks for a release. The system converts EARS or Given/When/Then formats into post-deploy verification steps, ensuring backend side effects and live smoke tests are validated after deployment.
Intense-VisionsGenerate structured product specifications with EARS acceptance criteria from GitHub issues.
jmaglyValidate phase-gate criteria and generate pass/fail gate reports.
All-The-VibesCreate or update GitHub pull requests from local Git changes.
wadvancedCreate GitHub pull requests after branch safety, test, and CI checks.
