deliverable-qa-packagelisted
Install: claude install-skill vincentdania/agent-skills-for-real-work
# Deliverable QA Package
Use when review findings must be turned into a document a client or senior colleague will actually read and act on. Findings in a chat window are not a deliverable; a formatted memo with clear decisions and an owner per action is.
## Outputs
Produce one or more of:
1. **Reviewer memo** — the formal assessment, suitable for sending to a client or for the project file.
2. **Redline summary** — the specific changes requested, line-referenced, suitable for returning to the consultant.
3. **Action tracker** — issue, owner, due date, status, decision required.
4. **Covering email** — short, sharp, pointing to the memo and stating the decision.
## Structure of a reviewer memo
1. **Header** — assignment title, document reviewed (with version/date), reviewer, date of review, distribution.
2. **Purpose and basis of review** — what the review assessed against (ToR, contract, quality standards) and what materials were available.
3. **Overall verdict** — one paragraph. Accept / accept with conditions / revise and resubmit / reject, plus the operational consequence.
4. **Summary of findings** — counts by severity, and the two or three findings that actually drive the verdict.
5. **Detailed findings** — numbered, each with: finding, location, evidence, impact on the assignment, required remedy, and severity.
6. **Requirement compliance table** — from the ToR register where available.
7. **Recommendations** — prioritised, each addressed to a named role, each wi