factory-qa

Coordinate QA, release preparation, and artifact validation for software projects.

10|5|Updated Jan 21, 2026
One-click install
npx skills add https://github.com/SylvainChabaud/spec-to-code-factory --skill factory-qa
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: factory-qa
Source: https://github.com/SylvainChabaud/spec-to-code-factory/tree/main/.claude/skills/factory-qa
Command: npx skills add https://github.com/SylvainChabaud/spec-to-code-factory --skill factory-qa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Skill coordinates the DEBRIEF phase by ensuring all mandatory QA artifacts are produced, validated, and ready for release, with auto-remediation support across gates.

Core Features & Use Cases

  • Enforces artifact generation: docs/qa/report or report-vN, docs/release/checklist or checklist-vN, and CHANGELOG.md, plus the release folder.
  • Orchestrates delegation to aqa agent, runs tests, exports release, and handles gate checks with retry logic.

Quick Start

Direct the agent to execute the DEBRIEF workflow and ensure gate 5 passes, then export the release.

Frequently Asked Questions about factory-qa

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate QA report and release checklist generation for software deployment?

Automating QA report and release checklist generation requires orchestrating a debrief workflow that validates mandatory artifacts like the QA report, release checklist, and CHANGELOG.md before exporting the release folder.

What is a Gate 5 release check and what artifacts are required to pass?

A Gate 5 release check is a quality gate requiring complete QA reports, release checklists, changelogs, and a validated release folder before software deployment. It ensures all mandatory documentation artifacts are produced and ready.

How do I coordinate automated remediation prompts when release validation fails?

Coordinating automated remediation prompts involves running gate checks with retry logic during the release debrief phase, delegating test execution to an aqa agent, and triggering strict template prompts for missing or invalid artifact files.

Can I use a structured workflow to validate release manifests for both brownfield and greenfield projects?

You can validate release manifests for brownfield and greenfield projects by applying a structured QA and release preparation workflow that enforces artifact generation, runs tests, and handles gate checks with automated retry logic.

What happens if a required file like the changelog or checklist is missing during the release export?

If a required file like the changelog or checklist is missing during release export, the workflow enforces strict prompts using predefined templates to auto-remediate the missing artifact and ensure gate 5 passes before proceeding.

Does the QA coordination workflow support versioned artifact generation for iterative testing?

The QA coordination workflow supports versioned artifact generation by enforcing the creation of versioned files such as report-vN and checklist-vN, ensuring iterative testing cycles maintain distinct documentation versions for release validation.