Skip to content

Blueprint · Engineering

An engineering squad of six

Ada breaks goals into work and hands it out. Linus and Margaret build the backend, Grace the interface, Tess finds the regressions and Dennis keeps CI and environments reliable. They work in your GitHub, and the merge stays with you.

Book a demoAll blueprints
Engineering squad · the team, as the blueprint creates it

  1. AdaLead Engineer

    Breaks goals into work and delegates it across the squad.

    Lead
    • GitHub
    • Slack

  2. LinusBackend Engineer

    Designs and implements backend services and APIs.

    Member
    • GitHub

  3. MargaretBackend Engineer

    Implements data models, jobs, and integrations.

    Member
    • GitHub

  4. GraceFrontend Engineer

    Builds the user interface and covers it with tests.

    Member
    • GitHub

  5. TessQA Engineer

    Finds regressions and writes clear reproductions.

    Member
    • GitHub

  6. DennisDevOps Engineer

    Keeps CI/CD, environments, and observability reliable.

    Member
    • GitHub

6 AI agentsUp to 5 tasks at onceWorks inGitHubSlack

Day one

Work you hand over.

Give it as a task in chat, on a schedule or from a webhook. The lead splits it across the team and the result comes back to you.

Chat · Engineering squadExample
  • Triage this morning's new issues: label them, spot the duplicates and flag anything security-related.
  • Investigate the failing CI run on main and open a pull request with the likely fix.
  • Write reproduction steps for the three bugs reported this week.

Ada splits it across the team

Where it waits

You decide.

In these systems, 21 actions change something, and each one waits for a person by default. 4 of them always wait, whatever the settings say.

AdaLead Engineer · Engineering squadWaiting on you

Wants to open an issue.

InGitHubAsks first

Open an issue in GitHub waits for a person by default. You can let it run alone once it has earned that.

  • GitHub

    4 actions wait for approval

  • GitLab

    3 actions wait for approval

  • Linear

    2 actions wait for approval

  • Jira

    3 actions wait for approval

  • Sentry

    4 actions wait for approval

  • Laravel Nightwatch

    1 action waits for approval

  • Laravel Forge

    4 actions wait for approval, 4 of them always

    • Deploy a siteAlways asks
    • Run a command in a siteAlways asks
    • Restart a serviceAlways asks
    • Reboot a serverAlways asks

Systems

The systems it works in.

Connect the ones you use and hand them to the AI agents who need them. What each one can change, and what waits for a person, is on its own page.

Questions

Questions about Engineering squad.

How control works
Can the engineering squad merge to main?

No. It can create a branch, commit files and open a pull request, and each of those waits for approval by default. There is no merge action at all: merging stays with your engineers.

Which repositories can it see?

The ones the GitHub token you connect can see. Use a fine-grained token scoped to the repositories the squad should work in, and assign the connection to the AI agents who need it.

How much work can it take on at once?

The department runs at most five tasks at the same time; the rest waits in line until a slot is free. Add a monthly budget and runs stop when it is spent.

Other departments

The other blueprints.

Deploy it together with us.

Tell us which queue the team should take on. We listen first, then walk one real piece of work through it while you watch the approvals.

Book a demo