Do I have to assign tickets to builders myself after I plan a project with Claude Code?

No, Tares has you assign nothing after you plan a project with Claude Code. Tares keeps the plan as tickets, each with the repo it changes, and the orchestrator hands out the work and starts the builders. A builder takes its tickets, opens pull requests and merges its own once they pass, and the reviewer reviews every pull request to a fixed bar.

How it works

You plan a project with Claude, and Tares keeps the plan as tickets. Each ticket carries the repo it changes, so the crew knows where every piece of work belongs. From then on, three roles in the software factory for Claude Code share the work:

• The orchestrator hands out work and starts builders itself, one per milestone and repo of a project.
• A builder takes its tickets, opens pull requests and merges its own once they pass.
• The reviewer reviews every pull request to a fixed bar and posts the verdict.

The crew keeps moving without you. tares factory crew up starts the crew and a watch in the background, and the watch brings back any session that stops, under the same name. The orchestrator wakes every 20 minutes and checks for work, so an idle crew still notices a new project, a stalled ticket or a merged pull request that unblocks the next one. A revived session reads its notes and the project on Tares, so it carries on from where the last one stopped. For more on how sessions keep running, see Run autonomous, self-running Claude Code sessions.

Set it up

Follow these steps in order. Steps marked local or cloud apply only to that kind of Tares.

1. Check that Claude Code is signed in, that gh is signed in with write access to the repos the crew works in, and that git, jq and curl are installed.

   gh auth login

2. Install the CLI.

   uv tool install tares     # or: brew install glassflow/tap/tares

3. Local only: start Tares, then in a second terminal start the MCP endpoint every crew session shares.

   tares up
   tares mcp --transport streamable-http

   Cloud only: sign in and pick your workspace in the browser. There is no MCP endpoint to start.

   tares login

4. Give Tares access to GitHub. On a local Tares, use Settings > GitHub. On Tares Cloud, use Connect GitHub.

5. Bring up the crew.

   tares factory crew up

6. Plan a project. Tares turns the plan into tickets, each with its repo.

   tares factory spec "what you want to build"

7. You assign nothing. When the orchestrator has a question for you, attach to it and answer.

   tares factory crew attach orchestrator

Build a software factory with Claude Code has the full Local and Tares Cloud setup, what you need on your machine and the commands to watch the crew.

What you get

• No ticket assignment. The plan becomes tickets, and the orchestrator starts one builder per milestone and repo.
• Builders that finish their own work. Each takes its tickets, opens pull requests and merges its own once they pass.
• A consistent review. The reviewer reviews every pull request to the same fixed bar and posts the verdict.
• Work that continues while you are away. The watch revives stopped sessions, and the orchestrator checks for work every 20 minutes.
• Decisions that stay yours. The crew does not guess at them. Questions wait on the desk until you answer, and the orchestrator brings them to you one at a time with a recommendation. When the plan does not answer a smaller question, the crew records an assumption and carries on, and the orchestrator confirms the assumptions with you once per milestone.

Merging is your setting. At L4-ship, a builder merges once the reviewer approves and CI is green. At L3-review, every merge waits for your yes. Releasing is off unless you ask for it, so without a releaser the crew stops when work is merged to main.

When something else fits

• If you want to approve each merge yourself, use the L3-review setting. Builders still pick up their own tickets, but every merge waits for your yes.
• If you want to decide what goes into a project, answer the orchestrator’s questions on the desk, and you keep the decisions that are yours without assigning any tickets.

Related