How do I know a project made of dependency upgrades is finished?

Tares tells you a project is finished when the orchestrator asks after the last milestone and you answer that it is done. Tares then marks the project Done with your words and moves it to the finished list on the Crew page. Stopping the crew is a separate step, tares factory crew down.

How it works

A project made of dependency upgrades follows the same path as any project you hand to the software factory for Claude Code. Every project has a page of its own with four steps across the top: Spec, Build, Review and Done. A progress bar below them has one segment per ticket.

• Each ticket shows a state: to do, in progress, in review, merged or blocked. A blocked ticket names the tickets it waits for.
• The builder opens a pull request for each ticket, and the reviewer posts a verdict on it. Once the verdict passes and CI is green, the builder merges.
• At the end of each milestone, the orchestrator brings you the choices the crew made on its own, the assumptions, in one question.
• After the last milestone, the orchestrator asks whether the project is finished.

The finish is your call. In the worked example on A project, end to end, the person deployed the result and answered that it was fully deployed, working and done. Tares marked the project Done with those words, with every ticket merged, and moved it to the finished list on the Crew page.

Set it up

1. Open the Crew page in the console, at http://127.0.0.1:8787/crew on a local Tares. The Projects list shows open projects with their builders, and finished ones folded below.
2. Open the project page and look at the Tickets fold. Each ticket shows the builder that held it, its pull request and its review rounds. The progress bar has one segment per ticket.
3. Answer the assumptions question at the end of each milestone in the orchestrator’s session. To make an answer stand from now on, say so, for this project or for every project.
4. When the orchestrator asks whether the project is finished, check the result yourself, then answer in your own words. Say what you verified, because Tares records your words.
5. Check that the project page shows the Done step. Your answer sits in the Decisions fold as you typed it, up to 4,000 characters, and the project now appears in the finished list on the Crew page.
6. When no project is left, the orchestrator asks whether to stop the crew. To stop every station, run:

tares factory crew down

Tares keeps the projects, tickets and answers, so the crew carries on from them the next time you bring it up. To pick up a finished project again, hand it to the crew again, for example with a follow-up spec:

tares factory spec "what you want to build"

If you are new to the software factory for Claude Code, start with Get started.

What you get

• A clear signal that the project is finished: the Done step on the project page, and the project in the finished list on the Crew page.
• A record in your own words. The answer that closed the project is in the Decisions fold, newest first, next to every other question the crew asked you.
• A record of what the crew decided alone. The Assumptions fold lists every choice the crew made on its own and whether you kept it.
• A per-ticket history in the Tickets fold: the builder, the pull request and the review rounds for each ticket.
• A choice about the crew. Finishing the project does not stop the stations. You stop them with tares factory crew down when you want to, and Tares keeps the projects, tickets and answers.

When something else fits

• If the project page still shows tickets in progress, in review or blocked, the project is not finished. Talk to the orchestrator to steer the work.
• If you have another project coming, leave the crew running and skip tares factory crew down.
• If a station shows Quiet, tares factory crew watch brings it back. Finishing a project does not require it.

Related