Review an external delivery draft in Claude Code
Check audience, commitments, supporting facts, tone, terminology, redaction, and traceability before an external delivery.
中文Install in Claude Code
A Claude Code project with the draft, supporting facts, and the approved scope that can be shared. This exercise is editorial review.
- Review `profiles/.claude/skills/compliance-delivery-checklist/SKILL.md` and its requirements at the pinned GitHub commit.
- Create `.claude/skills/compliance-delivery-checklist/` in your project and save the reviewed file as `.claude/skills/compliance-delivery-checklist/SKILL.md`.
- Start Claude Code from that project's root, then select `/compliance-delivery-checklist` in the slash menu.
Example task
A fictional customer draft contains `{audience:'customer',claim:'delivery in 2 days',approved:'no date yet',source:'internal summary only'}`. The team has made no date commitment and tracks the decision in a local note.What to check
Record `{claim:'delivery in 2 days',status:'unapproved'}` in the review. Remove the date promise from the draft so the owner can follow up, and log the actual supporting note internally.
Original SKILL.md on GitHub · Updated
Frequently asked question
How should a draft handle an unconfirmed customer delivery date?
Mark it as a failed check, verify the supporting facts and scope, and keep the source in an internal record. Use customer-appropriate terms and redact unapproved internal details.