Playbooks are "Strategic Recipes" for AI agents. While Skills describe what an agent can do with a tool, Playbooks describe how to orchestrate multiple tools to solve a complex engineering problem.
A playbook is a multi-step workflow that usually crosses the verticals of the EngOps Matrix:
- Code Signal: Merge Request or Pull Request (GitHub/GitLab).
- State Change: Task transition or comment (Jira/GitLab Issues).
- Knowledge Sync: Documentation update or publishing (Outline Ops/Confluence).
| Playbook | Verticals Involved | Goal |
|---|---|---|
| EngOps Triad | Code, Task, Knowledge | 100% sync from Merge to Documentation. |
| Jira-Outline Alignment | Task, Knowledge | Ensure documentation reflects ticket status. |
| Closed-Loop Engine | All | A conceptual code implementation of the Triad. |
We encourage contributors to add playbooks for every new high-frequency workflow (e.g., "Onboarding Audit," "Security Remediation Trace," etc.).
Moving from standalone skills to symphonic operations.