Engineering playbooks

Ready-made Engineering setups — each installs the agents, workflows, and documents for the job, then runs it with your approvals.

14 playbooks

Backend and API development

Trigger: When you start the “Backend and API delivery” workflow.
Job: Implement and verify the assigned backend or API change before human review.
Outcome: A tested implementation and pull request draft.

~2 h saved / run 2 Agents 1 Team 1 Workflow

Bug investigation & fix

Trigger: When you start the “Diagnose, fix, self-review, draft PR” workflow.
Job: Build a feedback loop, find the root cause, fix it with a test.
Outcome: A tested implementation and pull request draft.

~3.9 h saved / run 2 Agents 1 Team 1 Workflow

Database migrations

Trigger: When you start the “Database migration delivery” workflow.
Job: Plan, implement, and verify the assigned schema or data migration before human review.
Outcome: A tested implementation and pull request draft.

~1.5 h saved / run 2 Agents 1 Team 1 Workflow

Docs gardener & API doc writer

Trigger: On the “Garden docs” schedule.
Job: Diff changes against docs, draft the reconciling updates, edit, and draft a PR.
Outcome: Accurate documentation updates and a pull request draft.

~5 h saved / week 2 Agents 1 Team 1 Workflow

Frontend development

Trigger: When you start the “Build frontend feature” workflow.
Job: Build or optimize the feature, and draft a deploy-ready PR.
Outcome: A tested implementation and pull request draft.

~4.2 h saved / run 2 Agents 1 Team 1 Workflow

Issue triage & routing

Trigger: On the “Triage issues” schedule.
Job: Classify and dedupe, verify the actionable ones, then draft a triage summary for approval.
Outcome: An evidence-backed issue queue with proposed labels, routing, and next actions.

~2.2 h saved / week 2 Agents 1 Team 1 Workflow

Machine learning model development

Trigger: When you start the “Machine learning model delivery” workflow.
Job: Build and verify a reproducible model result.
Outcome: A tested implementation and pull request draft.

~4 h saved / run 2 Agents 1 Team 1 Workflow

Mobile app development

Trigger: When you start the “Mobile feature delivery” workflow.
Job: Implement and verify the assigned mobile change across its target platforms for review.
Outcome: A tested implementation and pull request draft.

~2 h saved / run 2 Agents 1 Team 1 Workflow

Pull request review

Trigger: When you start the “Code review” workflow.
Job: Read the diff, run the review and security passes.
Outcome: A prioritized code review with evidence and draft comments.

~2.2 h saved / run 2 Agents 1 Team 1 Workflow

QA review and test planning

Trigger: When you start the “QA plan delivery” workflow.
Job: Build and verify a risk-based QA and test plan.
Outcome: A verified, risk-based QA and test plan.

~1.5 h saved / run 2 Agents 1 Team 1 Workflow

Refactor & architecture improver

Trigger: When you start the “Refactor” workflow.
Job: Find the deepening opportunity, plan tiny commits, apply behind tests.
Outcome: A tested implementation and pull request draft.

~6.3 h saved / run 2 Agents 1 Team 1 Workflow

Security audit

Trigger: When you start the “Security audit delivery” workflow.
Job: Perform and verify an exploitability-first security audit.
Outcome: A tested implementation and pull request draft.

~3 h saved / run 2 Agents 1 Team 1 Workflow

TDD feature builder

Trigger: When you start the “TDD feature” workflow.
Job: Plan the feature, write failing tests, implement and refactor green, verify the suite.
Outcome: A tested implementation and pull request draft.

~5.3 h saved / run 2 Agents 1 Team 1 Workflow

Test gap filler

Trigger: On the “Fill test gaps” schedule.
Job: Find the behaviours that matter, backfill them in vertical slices, and draft a PR.
Outcome: A tested implementation and pull request draft.

~4.6 h saved / week 2 Agents 1 Team 1 Workflow

Don't see your workflow? Describe it.

A sentence or two about a recurring job is enough. We design the playbook that runs it and show you exactly what it saves.