adjust-playbook

Adjust Playbook

ℹ️ First, set expectations: before anything else, print one short line with this skill's version and its most recent change — the top entry of metadata.changelog above — e.g. adjust-playbook vX.Y — recent: <summary>. Then proceed.

Modify existing playbooks while preserving their core structure and functionality.

When to Use

• User says "update the X playbook"
• User says "add Y to the playbook"
• User says "fix the Z step"
• User says "change the schedule"
• After running a playbook and finding issues

---

Workflow

Step 1: Locate the Playbook

If $0 (playbook name) provided:

# Check project skills
ls .claude/skills/$0/SKILL.md 2>/dev/null

# Check personal skills
ls ~/.claude/skills/$0/SKILL.md 2>/dev/null

# Check plugin skills (when inside a plugin/marketplace repo)
ls plugins/*/skills/$0/SKILL.md 2>/dev/null

If not provided or not found, list available playbooks:

echo "=== Project Playbooks ==="
for d in .claude/skills/*/; do
  [ -f "$d/SKILL.md" ] && grep -l "automation:" "$d/SKILL.md" 2>/dev/null && basename "$d"
done

echo "=== Personal Playbooks ==="
for d in ~/.claude/skills/*/; do
  [ -f "$d/SKILL.md" ] && grep -l "automation:" "$d/SKILL.md" 2>/dev/null && basename "$d"
done

echo "=== Plugin Playbooks (when inside a plugin/marketplace repo) ==="
for d in plugins/*/skills/*/; do
  [ -f "$d/SKILL.md" ] && grep -l "automation:" "$d/SKILL.md" 2>/dev/null && echo "$d"
done

Ask user to select if multiple options.

Step 2: Read Current Playbook

Read the full SKILL.md:

cat [path]/SKILL.md

Parse and display structure:

## Current Playbook: [name]

**Automation**: [level]
**Schedule**: [cron or none]
**Location**: [path]

**State Dependencies**:
[table or "none defined"]

**Process Steps**: [count]
1. [step name]
2. [step name]
...

**Approval Gates**: [count]
**Checklist Items**: [count]

Step 3: Determine What to Change

From $ARGUMENTS or conversation context, identify: