Skip to Content
Tares

How do I write a spec a Claude Code crew can build bug fixes from in a Python backend?

Tares turns a bug-fix plan for your Python backend into a spec through the /tares:spec interview, which asks one question at a time and has a second model attack the plan. The result lands in a Tares project as a spec, milestones with acceptance checks, tickets with a working doc each, and an AGENTS.md. You then hand the project to the crew, and it builds the tickets into pull requests merged on main.

How it works

You do not write the spec by hand. You describe what you want in one line, and /tares:spec (or tares factory spec) turns it into a plan through an interview.

  • The interview. Claude Code asks you one question at a time. You answer in your own words, and you shape the plan as you go.
  • The attack. A second model attacks the plan, so weak points surface before any builder starts.
  • What lands in Tares. The plan is written into a Tares project: the spec, milestones with acceptance checks, tickets with a working doc each, and an AGENTS.md.
  • The hand-over. The interview ends by asking whether to hand the project to the crew. Say yes, and the orchestrator picks it up.

The crew is a set of Claude Code sessions running in the background on your machine. The orchestrator hands out work. Builders take one ticket each, work on their own branch and open a pull request. The reviewer reviews every pull request to a fixed bar, and a builder merges once the reviewer passes it and CI is green. Tares keeps the plan, the tickets, the reviews and your answers, so a crew that restarts carries on where it stopped. The Get started page covers the whole software factory for Claude Code.

Set it up

  1. Check what you need. Claude Code must be signed in on a plan that allows background sessions. You also need gh signed in with write access to the repos the crew works in, plus git, jq and curl. The Codex CLI is optional, if you want a second model to check every commit.

  2. Install the CLI and start Tares. Leave it running.

    uv tool install tares     # or: brew install glassflow/tap/tares
tares up                  # console on http://127.0.0.1:8787

  3. In a second terminal, start the MCP endpoint that every crew session shares. crew up and spec stop and tell you when it does not answer.

    tares mcp --transport streamable-http     # http://127.0.0.1:8788/mcp

  4. Give Tares access to your GitHub repos. Builders push with your gh login, but Tares reads the pull request, CI and merge state itself. Locally, add a GitHub token or App under Settings > GitHub. See GitHub for details.

  5. Bring up the crew. The first run asks how far the crew may go: whether it merges on its own after review and green CI or waits for your yes, whether it releases, whether a second model checks every commit, and how many builders run at once.

    tares factory crew up

  6. Open the repo of your Python backend, or a folder that holds its repos, and start the interview. Put the bug fixes you want in the quoted line.

    tares factory spec "what you want to build"

  7. Answer each question as it comes. When the plan is written and the second model has attacked it, say yes to the hand-over.

  8. Answer the crew’s own questions in the orchestrator’s session. They arrive one at a time, each with a recommendation.

    tares factory crew attach orchestrator

Run tares factory doctor at any point to check everything the crew needs.

What you get

  • A Tares project holding the spec, milestones with acceptance checks, and tickets that each have a working doc.
  • An AGENTS.md that the crew’s sessions share.
  • A plan that a second model has already attacked before builders touch your code.
  • Pull requests built by builders, reviewed by the reviewer to a fixed bar, and merged on main once CI is green.
  • A record on Tares of the plan, the reviews, the assumptions the crew made and the questions it asked you. You can check the choices the crew made on its own at the end of each milestone.
  • The Crew page in the console, which shows the question waiting for you, the stations, each project’s builders and the pull requests waiting for review.

When something else fits

  • For a small fix that does not need a crew, run tares factory session with your idea. It asks a few questions, writes a short spec and a ticket list on Tares, and builds it in your own Claude Code session.
  • If you want a human yes before every merge on one project, set that for the project. The rest of the crew can still merge on its own.

Still stuck? Get help

Last updated on
Quickstart