writing-checklist-communicationslisted
Install: claude install-skill msewell/agent-stuff
# Writing Checklist Communications
## Workflow
1. **Identify the checklist type** from the user's request or existing draft:
| Type | Use when |
|---|---|
| Request for Action | Asking someone for specific work by a deadline |
| Handoff | Transferring ownership of work completely |
| Meeting Agenda / Follow-Up | Making meetings produce decisions and actions |
| Process Runbook | Enabling first-attempt execution of a repeatable process |
If the type is ambiguous, default to Request for Action when the user needs something done.
2. **Read the template and guidance** for that type in [references/01-checklist-types-and-templates.md](references/01-checklist-types-and-templates.md).
3. **Produce the checklist communication.** Write from scratch using user-provided context, or rewrite an existing draft to match the template. Apply the item-writing rules below to every checklist item.
4. **Validate the output** against the anti-patterns and meta-checklist in [references/02-anti-patterns-and-validation.md](references/02-anti-patterns-and-validation.md). Fix any issues before presenting.
## READ-DO vs DO-CONFIRM
| Type | How it works | When to use |
|---|---|---|
| **READ-DO** | Read each item, then perform it immediately. | Unfamiliar processes, new team members, high-stakes sequential procedures. |
| **DO-CONFIRM** | Perform from memory, then verify with the checklist. | Experienced practitioners, routine tasks, post-completion verification. |
Most prof