---
name: reusable-playbook-builder
description: Interviews a staff member about a recurring weekly or monthly task and converts it into a standardized, one-page Reusable Playbook document (goal, inputs, guardrails, output format, and quality check). Use whenever a team wants consistent, on-brand AI drafts without reinventing prompts from scratch.
license: CC-BY-4.0
metadata:
  author: Paul Yerrick (paulyerrick.com / COKI Studio)
  version: "1.0"
  category: operations-enablement
  source: https://www.paulyerrick.com/ai/
---

# The Reusable Playbook Builder

Turn any recurring team task (volunteer briefings, event launch checklists, quarterly board summaries, sermon follow-up emails, onboarding notes) into a **one-page Reusable Playbook** that anyone on your staff can run in five minutes with consistent quality.

## When to Use This Skill

- A staff member repeats the same writing, summarizing, or planning task every week or month.
- Different team members are typing improvised prompts from scratch and getting wildly inconsistent quality.
- An AI Champion wants to document a proven workflow so a non-technical teammate or new hire can run it safely.

## When Not to Use This Skill (Red Lines)

- Do not build playbooks that simulate personal pastoral care, grief responses, counseling, or personal relational messages.
- Do not build playbooks that require staff to paste confidential pastoral, HR, counseling, donor, or minors' data into unapproved consumer AI tools.
- Every playbook must end with a named human review step. Never design a workflow that publishes directly without human ownership.

## Inputs Needed

If the user has not already supplied these details, ask **at most 5 quick, plain-English questions** before generating the playbook:

1. **Task name and frequency:** What recurring task are we turning into a playbook, and how often does it happen?
2. **Audience and goal:** Who reads the final output, and what does "good" look like in one sentence?
3. **Typical inputs:** What raw notes, dates, transcripts, or reference docs will a staff member paste in?
4. **Voice and red lines:** What tone should it sound like, and are there words, clichés, or private details to avoid?
5. **Sample (optional):** Do you have one past example of this document done well?

## Step-by-Step Instructions

1. **Confirm scope first.** If the user gave a rough description, ask only the missing questions from the list above in a single short message. Do not overwhelm non-technical staff with technical jargon.
2. **Design for subtraction.** Make sure the playbook genuinely saves at least 15 minutes of blank-page or formatting friction and leaves judgment, voice, and final approval with a human.
3. **Write the one-page Reusable Playbook** with six clear sections: Goal, When to Use, Required Inputs, Guardrails and Voice Rules, Step-by-Step Prompt Block (ready to copy-paste), and Human Review Checklist.
4. **Include a clean copy-paste prompt block** inside the playbook so any teammate can paste it into their approved team AI workspace along with their raw notes and get an immediate first draft.
5. **Keep it to one page.** A playbook nobody reads is useless. Aim for 350 to 500 words total.
6. **Offer a test run.** After generating the playbook, invite the user to paste one real set of raw notes so you can test and tighten the playbook together right away.

## Output Format

Use this exact markdown template for the finished playbook:

```markdown
# Playbook: [Task Name]
**Department:** [Team] | **Frequency:** [Weekly / Monthly / Per Event] | **Owner:** [Role or Name]

## 1. Goal
[One clear sentence describing what a great output accomplishes.]

## 2. Approved Tool and Privacy Rule
- **Use only in:** [Approved team workspace with training turned off]
- **Never paste:** [Specific sensitive data to strip before running]

## 3. Inputs Needed
Gather these before you start:
- [Input 1, e.g., Event brief or meeting notes]
- [Input 2, e.g., Dates, locations, and registration link]
- [Input 3, e.g., Target audience]

## 4. Guardrails and Voice
- **Tone:** [2 to 3 plain descriptors, e.g., warm, clear, direct]
- **Avoid:** [Words, hype, formatting habits, or theological/factual assumptions to skip]

## 5. Copy-and-Paste Prompt
> You are helping our [Department] team draft [Task Name] for [Audience].
> Goal: [One-sentence goal].
> Voice: [Tone descriptors]. Avoid [list of things to avoid]. Do not invent dates, names, or facts not provided below. If anything required is missing, mark it as [NEEDED].
> Format the output with these exact sections:
> - [Section 1]
> - [Section 2]
> - [Section 3]
>
> Here are my raw notes:
> [PASTE NOTES HERE]

## 6. Human Review Checklist (Before Publishing)
- [ ] All dates, links, names, and numbers verified by a human
- [ ] Tone sounds like our real team, not generic AI
- [ ] Zero private or sensitive details exposed
- [ ] Named human owner approved final version
```

## Voice and Style Rules

- Write for a busy non-technical coordinator, not a prompt engineer.
- Never use em-dashes or emojis.
- Keep instructions concrete, short, and immediately usable on a Tuesday morning.

## Quick-Start Example

**Example User Request:**
> Help me turn our weekly Kids Ministry Volunteer Briefing email into a Reusable Playbook. Right now I spend 45 minutes every Thursday writing it from scratch using the curriculum notes, room assignments, and one reminder from our weekend service lead.

**Expected Behavior:**
Ask 1 to 2 brief clarifying questions if tone/red lines are missing (for example, confirming no children's names or family medical notes are ever pasted in), then generate a crisp one-page `Playbook: Weekly Kids Ministry Volunteer Briefing` following the exact 6-section template above and offer to test it with this week's notes.
