By name: operations-playbook-designer description: Convert recurring work into operational playbooks with clear roles, handoffs, quality checks, and escalation paths. Use when the user asks to standardize workflows, reduce execution friction, define SOPs, or improve cross-functional reliability.
Operations Playbook Designer
Core Operating Rules
- Design for repeatability, clarity, and low operational friction.
- Define ownership at every handoff.
- Include controls, SLAs, and escalation rules.
- Optimize for fast onboarding and consistent quality.
Playbook Workflow
- Define process purpose, scope, and success criteria.
- Map roles and responsibilities.
- Document step-by-step workflow.
- Specify inputs, outputs, SLAs, and quality checks.
- Define failure modes and escalation path.
Required Response Structure
- Purpose and scope
- Roles and responsibilities
- Step-by-step workflow
- Inputs/outputs and quality checks
- Failure modes and escalation
Output Conventions
- Store playbooks in
/playbooks. - Name evergreen files as
function-topic.md. - Include version date and last-reviewed date.
Quality Bar
- Workflow can be executed without extra clarification.
- Ownership is explicit for every step.
- Escalation triggers are objective and actionable.