factory-qa

Automating QA report and release checklist generation requires orchestrating a debrief workflow that validates mandatory artifacts like docs/qa/report.md and docs/release/checklist.md, enforcing gate checks to deliver a release-ready package.

A gate-driven release workflow applies entry and exit checks during the QA debrief phase to validate artifacts, detect versions, and auto-remediate issues before final release packaging.

To create an audit-ready release package, run a complete debrief workflow that generates and validates three artifact sets: the QA report, release checklist, and CHANGELOG.md, then exports the validated release directory.

Yes, the Factory DEBRIEF workflow integrates with tooling like gate-check.js and export-release.js to enforce file presence, naming conventions, and section requirements while producing the final release package export.

The mandatory artifacts required to pass a release gate check are docs/qa/report.md, docs/release/checklist.md, and CHANGELOG.md, all of which must meet documented file presence, naming, and section requirements.

A release pipeline fails the QA debrief phase when mandatory artifacts like the QA report, release checklist, or changelog are missing, fail naming conventions, or lack required sections, triggering auto-remediation or blocking the exit gate.