Skip to main content

​
Explore the Playbook

Before writing your own workflows, explore what’s already available. Gump ships with 8 built-in workflows covering the most common engineering patterns.

​
List available workflows

gump playbook list

Gump Playbook

  cheap2sota          Start cheap, escalate on failure           (built-in)
  tdd                 Test-first, implement, verify              (built-in)
  full-cycle          Plan, implement, review, verify            (built-in)
  parallel-tasks      Decompose, build all items at once         (built-in)
  adversarial-review  Multi-agent review with arbitration        (built-in)
  bugfix              Reproduce first, then fix                  (built-in)
  refactor            Change structure, keep behavior            (built-in)
  gump-dogfood        How Gump builds itself                     (built-in)

​
Inspect a workflow

gump playbook show tdd
This prints the full YAML of the workflow — every step, every gate, every retry strategy. You can copy and customize it.

​
Which workflow to pick

The choice depends on what you’re doing: Everyday tasks — Start with cheap2sota. It’s the cheapest and works for most things. If you want a review step, use full-cycle. Quality-sensitive work — Use tdd for test-driven development, or adversarial-review for critical changes that need multi-agent review. Large specs — Use parallel-tasks if items are independent with disjoint file scopes. Otherwise, cheap2sota or tdd process items sequentially. Bugs — Use bugfix. It enforces the “reproduce first, fix second” discipline. Refactoring — Use refactor. It validates that existing tests stay green after every change. Each workflow is documented in detail in the Playbook section, with the full YAML, an explanation of how it works, and customization hints.

​
Override a built-in

If you want to customize a built-in workflow, copy it to your project: 
gump playbook show cheap2sota > .gump/workflows/cheap2sota.yaml
Edit the file. Project workflows take priority over built-in ones — next time you run --workflow cheap2sota, Gump will use your version. Workflows are looked up in this order:
  1. Project: .gump/workflows/<name>.yaml
  2. User: ~/.gump/workflows/<name>.yaml
  3. Built-in: shipped with Gump