Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.overcut.ai/llms.txt

Use this file to discover all available pages before exploring further.

Overcut Playbooks help you launch proven workflow templates without starting from scratch. Use the Playbook Catalog to browse templates in Overcut, preview how each one works, and add the right workflow to your workspace.
Use the Overcut Playbooks repository when you want to explore source files, read deeper implementation examples, or customize playbooks outside the product.

​
What are Playbooks?

Playbooks are pre-configured workflows that automate common software development tasks. Each playbook gives you a starting point that you can install in Overcut and then tailor to your team.

​
Why Use Playbooks?

Playbooks help teams move faster with reusable automation patterns:
  • 🚀 Start faster: Add a ready-to-use workflow instead of building every step manually
  • 🎯 Use proven templates: Begin with workflows designed for common engineering tasks
  • 🔧 Customize after install: Open the workflow in Workflow Builder and adapt it to your process
  • 📚 Learn by example: See how complete workflows are structured before creating your own

​
Browse the Playbook Catalog

The Playbook Catalog is the main place to discover workflow templates in Overcut. It gives you a dedicated browsing experience so you can compare options, open previews, and install the workflows that match your team’s needs.

​
Open the catalog

You can reach the Playbook Catalog from the main workflow experience in Overcut:
  • In the workflows area, select Add from Playbook to open the full catalog.
  • After completing onboarding, select Browse Playbooks to go directly to the catalog and explore recommended templates.

​
Search playbooks

Use the catalog search field to find playbooks by name or description. This helps you quickly narrow the list when you already know the kind of workflow you want to automate.

​
Filter by workflow type

Use the trigger category filters to narrow the catalog by workflow type. For example, you can focus on playbooks for pull requests, issues, scheduled work, or other trigger-driven automation patterns. If your search and filters do not match any results, the catalog shows an empty state so you can adjust your criteria and keep browsing.

​
Preview a playbook before installing

Select any playbook card in the catalog to open its detail view. In the detail view, you can review:
  • The playbook name
  • A short description of what it does
  • The first instruction or setup guidance included with the workflow
This preview helps you understand the playbook before adding it to your workspace.

​
Understand install status

The playbook detail view also shows whether a matching workflow is already installed in your workspace. If Overcut finds an installed workflow with the same playbook name, the detail view lets you know before you install again. This makes it easier to avoid confusion when your workspace already has the workflow you are looking for.

​
Install a playbook

When you find a playbook you want to use, select Add to Workspace. Overcut installs the workflow into your workspace so you can open it in Workflow Builder and customize it. After installation, Overcut confirms the workflow was added and gives you a direct path to open it in Workflow Builder.

​
If a matching workflow is already installed

If the playbook is already installed, Overcut highlights that status in the detail view and gives you an Open existing option. This takes you directly to the existing workflow instead of making you guess whether you should create another copy. You can still choose to install the playbook again if you want another copy to customize separately.

​
Create & Customize with AI

The playbook repository is also an AI-powered workspace. It includes built-in skills and rules for popular AI coding tools such as Claude Code, Cursor, Codex, and Gemini, so you can clone it and use your preferred agent to create new workflows or customize existing ones. 
git clone https://github.com/overcut-ai/overcut-playbooks.git
Open the repo in your AI coding tool and start asking:
  • “Create a new playbook that runs security checks when a PR is opened”
  • “Modify the code-review playbook to add a linting step”
  • “Explain how the create-pr-from-design playbook works”
The agent understands Overcut’s workflow format, trigger types, step actions, template variables, and agent tool capabilities.
For a complete walkthrough on using the playbook repo with AI agents, see Create & Edit Workflows.

​
Customizing Playbooks

​
Understanding Playbook Structure

Each playbook folder contains: 
playbook-name/
├── workflow.json          # Import this into Overcut
├── README.md              # Documentation and usage guide
├── step-id-name.md        # Prompt for step (filename = step ID)
├── another-step-id.md     # Each prompt file matches its step ID
└── special-agents/        # (Optional) Specialized agent instructions
    └── agent-name.md      # Instructions for configuring custom agents

​
Editing Prompts

Prompt filenames match step IDs in workflow.json, enabling AI-assisted updates:
  1. Edit the markdown file for the step you want to change
  2. Use AI to update the workflow.json file to match your changes
  3. Re-import the updated workflow into Overcut
Bidirectional Editing: You can edit prompts in the markdown files and have AI update the workflow, or modify the workflow in Overcut and export it back. The naming convention (step ID = filename) makes this seamless.

​
Special Agents

Some workflows require specialized agents with domain-specific expertise. When a playbook needs agents like “Security Engineer” or “Database Architect”, you’ll find configuration instructions in the special-agents/ folder.

​
Best Practices

​
Start Simple

Begin with a single playbook that addresses your most immediate need. Once you’re comfortable with the workflow, expand to additional playbooks.

​
Customize Gradually

Install the playbook first, test it, then customize prompts to match your team’s style. This helps you understand the workflow before making changes.

​
Monitor and Iterate

Track how playbooks perform in your environment. Adjust prompts based on what works well and what needs improvement. Each team’s codebase and process is different.

​
Combine Playbooks

Many playbooks work well together. For example:
  • Requirements Document Generation → Technical Design Proposal → Create PR from Design
  • Auto Root Cause Analysis → Fix Review Comments

​
Next Steps

​
Contributing

Found a playbook that works well for your team? Consider contributing improvements back to the community. The playbooks repository welcomes:
  • New playbooks for common workflows
  • Improvements to existing playbooks
  • Better prompts and documentation
  • Bug fixes and edge case handling
See the Contributing Guide for details.