QA Gate

---

name: qa-gate

description: Final quality validation gate for any artifact before human review. Run this skill on documents, skills, PRDs, blog posts, or code artifacts to validate factual accuracy, tone consistency, completeness, structural integrity, operational soundness, and sensitive data handling. Use when you need to "QA gate this", "validate before publish", run a "final check", perform "quality validation", proofread this, fact-check this, or otherwise validate, QA, or quality-gate an artifact before review, release, or publication.

---

# QA Gate

Final release gate for any artifact before human review. Every document, skill, blog post, PRD, or code output should pass this gate before the principal sees it.

This is **not** a code review skill. It is a release gate that determines whether an artifact is ready to move forward.

When to Use

Optional Mode

Process

Step 1: Read the artifact completely

Read the entire file. Do not skim. Understand the structure, voice, and intent.

Step 2: Validate against 6 dimensions

**1. Factual Accuracy**

**2. Tone & Voice Consistency**

**3. Completeness**

**4. Structural Integrity**

**5. Operational Soundness** (for technical documents)

**6. Sensitive Data Check**

Step 3: Produce gate verdict

Output must include a clear gate result:

PASS — ready for human review

or

PASS WITH FIXES
- MINOR [location]: issue description

or

FAIL
- CRITICAL [location]: issue description
- MAJOR [location]: issue description
- MINOR [location]: issue description

Step 4: If FAIL, fix and re-validate

Fix all CRITICAL and MAJOR issues. Re-run the gate. Only present to principal after PASS or PASS WITH FIXES.

Integration with PRD Workflows

Add to any PRD as a verification step:

### D) QA Gate
- [ ] Run QA Gate on all major artifacts produced in this PRD
- [ ] All artifacts must PASS before marking PRD complete
- [ ] Fix any CRITICAL or MAJOR issues identified

Output Format

Write validation report to: `qa-gate/YYYY-MM-DD-<artifact-slug>.md` (relative to your workspace or evidence directory)

Use this structure:

# QA Gate Report: <artifact name>

## Gate Result
PASS | PASS WITH FIXES | FAIL

## Artifact Type
Document | Skill | PRD | Blog Post | Code Artifact | Other

## Findings
- SEVERITY [location]: issue description

## Summary
Brief explanation of why the artifact passed, passed with fixes, or failed.

Quality Standards

A PASS with only MINOR issues is acceptable. CRITICAL or MAJOR = must fix first.