What happens when the reviewer asks for changes to framework migrations?

Tares sends the pull request back to the builder, which makes the changes, and the reviewer runs a second round. Smaller findings the reviewer notices outside the ticket become a new ticket in the plan. Your framework migrations pull request goes through the same review as any other pull request in the software factory for Claude Code.

How it works

The software factory for Claude Code reviews every pull request the same way, so a pull request for framework migrations follows the usual round trip.

• The builder works through its tickets one at a time. For each ticket it makes a branch, does the work and opens a pull request.
• The reviewer reviews the pull request and posts its verdict.
• When the reviewer asks for changes, the builder makes them and the pull request goes to a second round. Most tickets pass on the first round. In the project walked through on A project, end to end, two tickets took a second round and passed on it.
• Once the verdict passes and CI is green, the builder merges. Your choice at crew up sets how far the crew may go. In one project the crew merged on its own after a pass, and in another it waited for the person’s yes before every merge.

The reviewer can also find smaller issues outside the ticket it is reviewing. The orchestrator turns them into a new ticket and places it in the plan. In the walkthrough project, that ticket went into the second milestone before the integration tests, and the builder fixed the findings there. The plan grew by one ticket on its own.

The orchestrator records that choice as an assumption. At the end of the milestone it brings you its assumptions in one question, and you decide whether to keep them.

Set it up

You do not configure review rounds. They are part of how the crew builds a project. To get a project into the review loop, follow Get started, which needs Claude Code signed in.

1. Install the CLI and start Tares locally. Start the MCP endpoint in a second terminal, because on a local Tares the crew reaches Tares only through it.
2. Bring up the crew.
3. Plan the project with a spec. Describe the framework migrations work you want. The spec session produces a plan, an AGENTS.md for the project and milestones with acceptance checks.
4. Say yes when asked to hand the project to the crew. The orchestrator starts a builder for the first milestone.
5. Watch the review rounds on the project page. The Tickets fold shows each ticket with the builder that held it, its pull request and its review rounds.

tares up
tares mcp --transport streamable-http
tares factory crew up
tares factory spec "what you want to build"

Run tares up and tares mcp in separate terminals. On Tares Cloud, run tares login instead and skip the MCP step.

Open the Crew page in the console at http://127.0.0.1:8787/crew to see each station, its state and the pull requests waiting in the review queue. Answer the crew’s questions in the orchestrator’s session. Your answers are kept in the Decisions fold, as you typed them.

What you get

• A visible round trip. Each ticket shows its state (to do, in progress, in review, merged or blocked) and its review rounds, so you can see that a pull request went back for changes and passed on the next round.
• A pull request that merges only after the reviewer passes it and CI is green.
• A plan that adapts. Smaller findings outside the ticket become their own ticket instead of being lost or bloating the pull request under review.
• A record of the choices the crew made on its own, listed as assumptions with the tickets they touch and the builder that made them.
• A history of your answers in the Decisions fold, in your own words.

When something else fits

• If you want to steer a ticket mid-build, talk to the orchestrator rather than the builder, because it answers the builders and brings you what needs you.
• If you want a tighter merge gate, choose at crew up how far the crew may go, so merges wait for your yes.
• If a station shows Waiting for you, open its session in a terminal and answer there, or say “continue”.

Related