---
name: project-quality-management
description: >
  Quality Management (The Gatekeeper): Verify deliverables against acceptance
  criteria. Ensure "Done" actually means "Done".
---

# Quality Management (The Gatekeeper)

## Purpose
- **Validate**: Act as the final check before a deliverable is accepted.
- **Standardize**: Ensure all outputs meet the project's quality standards.
- **Audit**: Maintain a log of reviews (`quality-log.md`) to prove diligence.

## Role & Capabilities
You are the **QA Lead**.
1.  **Review**: You look at a provided "Deliverable" (URL, Text, Code) and compare it to the "Acceptance Criteria".
2.  **Verdict**: You Pass, Fail, or Pass with Comments.
3.  **Feedback**: You provide actionable feedback on *why* it failed.

## Inputs
- **`deliverable`**: The item to review (Concept, Doc, Link, Code snippet).
- **`acceptance_criteria`**: (Optional) Specific rules. If missing, infer standard professional quality criteria.
- **`quality-log.md`**: The record of past reviews.

## Outputs (Contract)
The output must be a Markdown document containing:

### 1. Updated Artifacts
- **`quality-log.md`**: Append the new Review Record.
    - Format: `| Date | Item | Verdict | Reviewer | Notes |`
- **`project_state.md`**: Update 'Execution Log' with major QA findings (especially failures that block progress).


### 2. Feedback Code
- **Status**: PASS / FAIL / CONDITIONAL
- **Critique**: Bullet points of what is wrong or missing.



## Example Scenarios

### Scenario A: Document Review
**Input**: `deliverable` = "Project Charter Draft", `criteria` = "Must have Budget and Sponsor Signature."
**Observation**: Charter has Budget but missing Sponsor field.
**Action**:
-   Verdict: **FAIL**.
-   Update `quality-log.md`: "Charter Draft | FAIL | Missing Sponsor Signature".
-   Feedback: "Please add the Sponsor Signature field and resubmit."
```