Playbooks

These playbooks document reusable ways to run an agent swarm in production. Each one corresponds to a "Known Use Case" from the agent-swarm README and gives you the same three things:

1. Agents — which roles do the work, with links to the official agent templates.
2. Tools & Skills — what each agent calls, grouped by source (see the legend below).
3. Workflows / Schedules — the actual scheduled jobs and on-demand flows that drive the use case.

Skill-source legend

Every skill referenced in a playbook is tagged with one of three sources:

Agent links always point at the matching official template so new swarm users can clone the template as a starting point.

The ten playbooks

• Feature Development — Slack/Linear request → research → plan → implementation PR → review → merge.
• Lead Prospecting — Daily discovery + drafting + scheduling, with a human approval gate before sending.
• Content Generation — Topic mining, blog/social/meme production, all gated by a different-model-family LLM-as-judge reviewer and finalized by humans.
• UX Command Center — Weekly UX audits, agentic session recording, design-system enforcement, telemetry-driven proposals.
• Proactive Customer Support — Per-customer working directories, scheduled value-showcase reports, post-meeting follow-ups.
• Observability Alert Management — Datadog/New Relic/Sentry/SigNoz alerts kick off fixes or proposals; noise gets filtered before agents act.
• Code Health — Recurring Code Maat + D3.js reports for any Git repository, refreshed weekly by default and published to one stable Page URL.
• DORA Metrics — Recurring DORA reports with exact deployment frequency and lead time from release tags, plus clearly labeled proxy CFR and recovery-time estimates.

• Reports from Multiple Sources — Join your data warehouse, analytics, billing, search, and observability into one swarm.
• Self-Documenting & Release Reports — Auto-update docs, generate release notes, render release videos with Remotion + browser captures.

Hot patterns

Patterns that recur across multiple playbooks — read these too if you want to skip the same mistakes we made:

• Litmus Tests — LLM-as-judge quality gates that hard-reject sub-bar output.
• Drain Loops — turn one big ticket into stacked, individually-reviewable PRs, then a merge loop.
• HITL Gates — pause a workflow until a human approves in Slack.
• Per-Customer Working Directories — persistent per-account context in agent-fs.
• No-op When Nothing Changed — detect "nothing changed" and skip silently.