Skip to Content
Tares

What happens when the reviewer asks for changes to small features?

Tares runs a second review round: the reviewer asks for changes, the builder makes them, and the reviewer checks the pull request again. Smaller findings the reviewer spots outside the ticket become a new ticket that the builder fixes in the same milestone. The ticket records every review round, so you can see how many passes it took.

How it works

The software factory for Claude Code moves each ticket through build and review the same way, whatever the size of the feature.

  • The builder works through the tickets one at a time. For each ticket it makes a branch, does the work and opens a pull request.
  • The reviewer reviews every pull request and posts its verdict.
  • When the verdict passes and CI is green, the builder merges. You choose at crew up how far the crew may go on its own, and a project can also wait for your yes before every merge.
  • When the reviewer asks for changes, the builder makes them and the next round runs. In the project followed on A project, end to end, most tickets passed on the first round. Two tickets took a second round, and in another project one ticket took two rounds, with the second one passing.
  • The reviewer can also find smaller issues outside the ticket it is reviewing. The orchestrator turns them into a new ticket. In that project it became T8, placed in the second milestone before the integration tests, and the builder fixed the issues there. The plan grew by one ticket without anyone editing it.
  • The orchestrator records that choice as an assumption, here A3. At the end of each milestone it brings you its assumptions in one question, and you say whether to keep them.

Set it up

You do not configure review rounds. They are part of how the crew runs a project. To get a crew building and reviewing, follow the order from Get started.

  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.
  2. Install the CLI, then start Tares locally and, in a second terminal, the MCP endpoint every crew session shares. On Tares Cloud, run tares login instead and skip the MCP step.
  3. Give Tares access to GitHub, then bring up the crew and plan the project.
uv tool install tares     # or: brew install glassflow/tap/tares
tares up
tares mcp --transport streamable-http
tares factory crew up
tares factory spec "what you want to build"
  1. Open the Crew page in the console, at http://127.0.0.1:8787/crew on a local Tares. Pull requests waiting for the reviewer appear in a review queue.
  2. Open the project page and unfold Tickets. Each ticket shows the builder that held it, its pull request and its review rounds. A ticket the reviewer sent back shows more than one round.
  3. Open Assumptions to see the choices the crew made on its own, including any ticket it added from the reviewer’s smaller findings. At the end of a milestone, answer the orchestrator’s question in its session. To make an answer stand from now on, say so, for this project or for every project.
  4. To steer the work in between, talk to the orchestrator. If a station is waiting for you, open its session in a terminal and answer there, or say “continue”.

What you get

  • A clear round trip: changes requested, changes made, a second pass, then the merge once the verdict passes and CI is green.
  • A record on each ticket of the builder, the pull request and every review round.
  • Smaller findings that do not get lost. They become their own ticket in the plan instead of piling onto the ticket under review.
  • A written assumption for every choice the crew made on its own, so you can keep it or change it at the end of the milestone.
  • A project page that shows the progress as one segment per ticket, so a new ticket appears in the bar as the plan grows.
  • The same review rhythm for every project the crew builds, from the first ticket to the last.

When something else fits

  • If you want to approve each merge yourself, choose that at crew up. The crew then waits for your yes before every merge, and each approval is stored in the Decisions fold in your own words.
  • If you disagree with a ticket the orchestrator added, say so when it asks about the assumptions at the end of the milestone, or talk to the orchestrator before then.
  • If you are new to the factory, start with Get started before reading the full walkthrough.

Still stuck? Get help

Last updated on
Quickstart