qa-evidence-requirements

To generate a QA evidence checklist for a bug fix, the Skill automatically creates a tailored list requiring proof of the original error, root cause, before/after code comparison, and a regression test.

Evidence verification in software development workflows is the process of checking the presence and quality of required evidence items to enforce quality gates before code is merged or released.

Yes, you can block a release based on missing critical QA evidence. The Skill integrates with QA workflows and uses severity levels to prevent releases when required evidence items are absent.

Yes, this evidence checklist tool supports dependency updates and refactoring tasks. It generates tailored checklists based on the specific type of development task being performed.

You enforce quality gates with required and optional evidence items by defining severity levels within the Skill, which guides QA through verification and blocks releases if critical evidence is missing.

The best way to automate checklist generation for feature implementations is using this Skill, which automatically creates tailored evidence checklists based on the task type to ensure all necessary quality gates are met.