# Deliverable Review

Quality review of completed work against the original brief. When a project has produced deliverables and someone needs to confirm they meet the standard before handoff, sign-off, or client delivery.

This is not a progress check — it's a quality gate. The work should be substantially complete before entering review mode.

## Process

### Establish the Brief

Retrieve the original brief, spec, or agreement that defines what was promised. This may be:
- The locked execution plan from a sprint (if the work came from a structured project)
- A quote or proposal sent to a client
- A verbal agreement captured in task notes or memory
- A regulatory requirement or compliance checklist

If no written brief exists, construct one from the available evidence and confirm it with the user before proceeding.

### Review Each Deliverable

For every item in the brief:

- **Delivered as promised** — the deliverable meets the agreed specification. State what confirms this.
- **Delivered with deviation** — the deliverable exists but differs from what was agreed. Describe the difference and whether it's acceptable.
- **Not delivered** — the deliverable is missing. Determine whether it was intentionally deferred, forgotten, or blocked.
- **Over-delivered** — work was done beyond what was promised. Note whether this adds value or represents scope creep.

### Quality Assessment

Beyond checking against the brief, assess overall quality:
- Is the work client-ready? Would you be comfortable handing this to the end recipient?
- Are there obvious errors, omissions, or rough edges?
- Does the work reflect the agreed standard of care for this type of deliverable?
- If this work will be built upon later, is the foundation solid?

### Verdict

Summarise the review:
- **Pass** — all deliverables meet the brief, quality is acceptable. Ready for handoff.
- **Conditional pass** — most deliverables meet the brief, but specific items need attention before handoff. List them.
- **Fail** — significant gaps between what was promised and what was delivered. List every gap and what's needed to resolve it.

Record the verdict in the project task notes: `[PROJECT:PHASE] Review — {Pass/Conditional/Fail}: {summary}`.

## When to Use

- "Can you check the documents before I send them to the client?"
- "Review the quote package for the Henderson project"
- "Is everything ready for handoff?"
- "Check if we've done everything we promised"
- "The work is done — review it against the original spec"