Playbook

A playbook is the reusable form of an agentic workflow. The workflow is what actually runs when an event fires; the playbook is the packaged template you start from to get there. In Overcut, that template is a concrete artifact: a workflow definition you import into the builder, an editable prompt for each step, and the triggers and documentation that come with it. You can pick a prebuilt playbook, such as PR review or root cause analysis, or author your own.

That packaging is what makes organizational standardization practical. Without playbooks, every team that wants automated code review or CI fixing designs the workflow themselves, and the results drift apart. With them, one proven process is imported, adapted to each codebase, and run the same way everywhere. Overcut ships playbooks both in the product and as open playbooks in a public repository, so a team adopts a known-good starting point and keeps improving it, rather than starting from a blank canvas each time.

A team wants failing builds handled without someone babysitting the CI tab. Instead of designing the automation, they import the Fix CI playbook. It arrives complete: a trigger bound to a failed CI run on a pull request branch, two steps each with an editable prompt, one that analyzes the failure and finds the root cause and one that applies the fix and commits it, and documentation describing how it runs. They point it at their repository, adjust the analysis prompt for their stack, and add an approval gate so a human signs off before any push. From then on, every failing build on a PR triggers the configured workflow. When a second team needs the same thing, they import the same playbook for their service rather than reinventing it. One process, proven once, reused everywhere.