What does the crew do with problems the reviewer finds outside the ticket it is reviewing?

In the example project, the orchestrator of the Tares software factory for Claude Code turned the reviewer’s smaller out-of-scope findings into a new ticket, T8. It placed T8 in milestone M2 before the integration tests, and the builder fixed the findings there. The plan grew by one ticket on its own, and the crew recorded the choice as an assumption for you to keep or change.

How it works

The A project, end to end page follows one real project through the software factory for Claude Code. The reviewer reviews every pull request and posts a verdict. Once the verdict passes and CI is green, the builder merges.

In that project, the reviewer also found smaller issues outside the ticket it was reviewing. Here is what happened next:

• The orchestrator turned those findings into a new ticket, T8.
• It placed T8 in M2, “payout history stays as it was”, before the integration tests.
• The builder fixed the findings in that ticket.
• The plan grew from seven tickets to eight without you editing it. The project ended with eight of eight tickets merged.

The crew treats this as a choice it made on its own. When it meets something the plan does not cover, it picks the sensible answer, writes it down as an assumption and carries on. Here the choice was recorded as assumption A3: the reviewer’s smaller findings became ticket T8.

The orchestrator brings its assumptions to you together in one question at the end of each milestone. In this project, the person kept all five assumptions, A3 included.

Set it up

You do not configure anything special for this. The orchestrator, reviewer and builder run as part of the crew, so you bring up the crew and give it a project. The steps below are for a local Tares. The full walkthrough is in 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.
3. Start Tares locally.
4. In a second terminal, start the MCP endpoint every crew session shares.
5. Bring up the crew.
6. Plan a project with a spec.

gh auth login
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"

On Tares Cloud, run tares login instead of tares up and tares mcp. Then run tares factory crew up and tares factory spec.

Once the project is handed to the crew, watch it on the Crew page of the console, at http://127.0.0.1:8787/crew locally. Open the project page and unfold Tickets to see each ticket with the builder that held it, its pull request and its review rounds. Unfold Assumptions to see each choice the crew made on its own and whether you kept it.

What you get

• A visible record. The Tickets fold shows every ticket, including one the orchestrator added mid-build, with its builder, pull request and review rounds. The progress bar has one segment per ticket.
• Findings placed in the plan. In the example, the smaller findings sat in M2 ahead of the integration tests, so the builder fixed them in the milestone they belonged to.
• Your say at the end of the milestone. The choice appears under Assumptions, with its tickets and the builder that made it. You keep it or change it when the orchestrator asks. To make an answer stand from now on, say so, for this project or for every project.
• Steady progress. The crew did not stop to ask you about the smaller findings. The example project went from spec to eight merged pull requests in about three hours and asked the person five questions in total.

To steer the work at any point, talk to the orchestrator in its session.

When something else fits

If a finding is large, or changes what you want built, raise it with the orchestrator yourself rather than waiting for the end-of-milestone question. You can also reject an assumption when the orchestrator brings it to you. To change the plan before the crew starts, go back to tares factory spec, which is where the plan and its milestones are written.

Related