Understaffed

Every task goesthrough you twice

You hire AI roles and assign them tasks from a board. You approve the spec before any code is written, and the code before it reaches your branch.

Try it: read the criteria of task #6 and approve its spec, or request changes.

  1. Backlog 4

    • Awaiting your approval

      Dark mode for the admin panel

      #6Medium0/8Frontend

      Acceptance criteria 3

      • Theme follows the system
      • User choice
      • Sufficient contrast

      The spec passes OpenSpec validation.

    • Product search with filters

      #9MediumFrontend

    • End-to-end tests for checkout

      #10MediumQA

    • Serve product images as WebP

      #11Low

    + Add task

  2. To do 2

    • Discount coupons at checkout

      #7High0/3Full-stack

    • Low-stock email alert

      #8Low0/2Backend

  3. In progress 1

    • Running

      Rate-limit login attempts

      #5Urgent3/4Backend

  4. In review 1

    • Waiting for your review

      Export orders to CSV

      #4High5/5Backend

  5. Done 3

    • Paginate the order list

      #1High4/4Backend

    • Validate the email at sign-up

      #2Medium3/3Backend

    • Fix VAT rounding in the cart

      #3Urgent2/2Backend

Demo with the storefront sample project; the run is simulated.

In the app, this task moves on like this:

  1. Approve spec: it moves to To do.
  2. Run: its role does it on its own branch and it moves to In review.
  3. Approve: the code reaches your branch in one commit.

How a task reaches your branch

The spec, before any code is written. The code, before it reaches your branch.

  1. First, the spec

    You write the task and its role drafts the change in OpenSpec, an open spec format that lives in files in your repository: proposal, requirements with scenarios, design and tasks. You approve it or request changes.

    Acceptance criteria in the spec of task #6: “Theme follows the system”, with its requirement and the “Dark system” scenario
  2. Then, the work

    The role works on its own branch with Claude Code, the CLI you already have and already pay for. Understaffed stores no keys.

    How every run is launched (abridged):

    claude -p
      --output-format stream-json
      --permission-mode acceptEdits
      --tools Read,Glob,Grep,Edit,
              Write,Agent,Skill
      --append-system-prompt-file
          <role instructions>
  3. Finally, the code

    You review the diff and approve it, send it back with a comment or discard it. Approving brings it to your branch in one commit, with your hooks and signature.

    Diff of src/orders/orders.routes.ts in the review of task #4, with its added and removed lines

What awaits your decision, at a glance

The Status view brings together what awaits your approval, what is running, the activity and the cost per role. In a group, across all of its repositories.

The “Waiting on you” list of the Online store group: five tasks from its three repositories, three awaiting your approval and two your review
Waiting on youThe specs and code waiting for your approval across the three repositories of “Online store”.On this screen, swipe each image to see all of it.
The “Running” strip: the Backend role is running storefront task #5 and has been for under a minute
RunningWhat is running, which role is doing it and since when.
Cost and time over the last 30 days per role in the storefront project: Backend, Full-stack and Frontend
Cost per roleWhat the runs of each role have cost over the last 30 days.Cost reported by the provider; with a subscription it is an estimate.

Hire the roles you need

Start from a template or a blank role. Every role has its instructions, its model and its permission to run commands.

Pick a template to read its instructions

  • Product analystIn the dialog

    Your strength is understanding the problem before the solution: what the user needs, why, and how everyone will know it is solved.

  • Full-stack developerIn the dialog

    You work end to end: data, logic, interface and tests.

  • Frontend developerIn the dialog

    You build interfaces that are clear, accessible and consistent with the project’s design system.

  • Backend developerIn the dialog

    You take care of data, APIs, business logic and their reliability.

  • TesterIn the dialog

    Your goal is that what gets delivered does what the spec says, edge cases included.

Hire: Backend developer

Name

Backend developer

Instructions498 / 8000

You are a backend developer. You take care of data, APIs, business logic and their reliability. - Design data changes carefully: safe migrations, constraints in the database and nothing that loses existing information. - Validate every external input and return clear, stable errors. - Think about concurrency, transactions and partial failures. - Follow the project's architecture and conventions; do not add dependencies without a reason. - Cover new logic with tests, including the error cases.

Model

Claude Code default

Permissions

Run commands

The app’s hire dialog, with the full instructions of the chosen template.

On your computer first. Then with your team.

An account is optional: you only need one to sync your computers and collaborate with other people.

  • No account

    This computer

    • Without an account signed in, the app doesn’t connect to any server.
    • Each role works on its own branch; approving brings the work to your branch in one commit.
    Foot of the board sidebar with no account: “No account”, “Sign in in Settings” and the Send and Receive buttons inactive
  • With an account

    Your computers

    • You sign in with your email and a code sent to you, with no passwords.
    • Send and Receive carry the whole state from one computer to another, task branches included, and it only asks you about what conflicts.
    Your computers in the account settings: Emma’s laptop, this computer, and Office desktop, with the name this computer shows on the other one
  • As a team

    People and agents

    • You share a project or a group and invite people by email.
    • The board syncs live and two people never work on the same task at once. The account works with your own server.
    Shared backlog: task #9 running on Daniel Park’s computer and #10 being specified for Emma Walsh

Works with what you already use

Understaffed doesn’t install git or Claude Code, but it explains how when they are missing.

Get early access

Understaffed is in early access for Windows and macOS. Leave your email and we will let you know when you can install it.

Joining doesn’t create an Understaffed account.

Your email goes to our inbox and we only use it to tell you when you can install Understaffed. To leave the list, write to [email protected].

This form needs JavaScript. Without it, write to [email protected] and we’ll add you.