client-delivery-auditorlisted

Audit final client deliverables against the agreed scope, verify files and links, and prepare a clear handoff with an unsent delivery message. Use when a user asks to check a delivery package, find missing or unverified items, prepare final files, create a client handoff, draft a delivery email, separate private evidence from public proof, or confirm that a project is ready to send.
jqaisystems/jqai-ai-skills · ★ 2 · AI & Automation · score 73

Install: claude install-skill jqaisystems/jqai-ai-skills

# Client Delivery Auditor Turn completed project work into a checked delivery package with clear status, instructions, and communication. ## 1. Reconstruct the agreed delivery scope - Confirm the project root, delivery milestone, recipient, and intended delivery channel. - Read the latest brief, proposal, feedback, approval notes, and existing handoff material. - Use the latest explicit decision when it changes earlier scope. - Do not infer pricing, rights, approval, deadlines, or included deliverables. - Preserve exact project names, links, dates, formats, and file requirements supplied by the user. ## 2. Audit every promised item Classify each deliverable as: - `present and verified`: exists, opens correctly, and matches the agreed format - `present but unverified`: exists but still needs an appropriate check - `partial`: identifiable work remains - `missing`: promised but not found - `excluded`: explicitly removed from scope - `awaiting client`: depends on approval, content, access, or another client action Check filenames, formats, dimensions, variants, links, versions, accessibility needs, and usage instructions relevant to the project. Do not report the delivery as ready while required items are missing or unverified. ## 3. Prepare the handoff - Use [assets/client-delivery-handoff-template.md](assets/client-delivery-handoff-template.md). - Follow an existing delivery structure when one is already established. - Include only final or intentionally shared files i