How do I know a project made of internal refactors is finished?

Tares marks a project finished when you say so. After the last milestone, the orchestrator asks whether the project is finished, and when you answer that it is done, Tares 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. A project made of internal refactors follows the same path as any other project in the software factory for Claude Code.

How it works

The software factory for Claude Code tracks every project on its own project page, and the finish line is your decision.

• The project page shows four steps across the top: Spec, Build, Review and Done. A progress bar has one segment per ticket.
• The Tickets fold lists the milestones with their acceptance checks. Each ticket shows its state (to do, in progress, in review, merged or blocked), the builder that held it, its pull request and its review rounds.
• The reviewer reviews every pull request. Once the verdict passes and CI is green, the builder merges.
• At the end of each milestone, the orchestrator brings you the assumptions the crew made on its own, in one question, and you keep or change them.
• After the last milestone, the orchestrator asks whether the project is finished. Your answer is the signal. Tares marks the project Done with your words, records every ticket as merged, and moves it to the finished list on the Crew page.

The project walkthrough follows one project through this ending. The person deployed it, answered that it was fully deployed, working and done, and Tares recorded those words.

Set it up

You do not configure anything to finish a project. Follow the project to the end and answer the orchestrator’s question. If you have not brought up the crew yet, start with Get started.

1. Open the Crew page in the console, at http://127.0.0.1:8787/crew on a local Tares. The Projects list shows your open projects, with the finished ones folded below.
2. Open the project page and check the Tickets fold. Each milestone should show its tickets merged, and the progress bar should be full.
3. Answer the orchestrator’s end-of-milestone question about assumptions. Each assumption names the tickets it touches and the builder that made it. Your answers appear in the Decisions fold as you typed them, up to 4,000 characters.
4. Check the result yourself, in whatever way proves the work is complete for your project. When the orchestrator asks after the last milestone whether the project is finished, answer in its session in your own words, for example that it is done.
5. Confirm on the Crew page that the project moved to the finished list, and that the project page reaches Done.
6. With no project left, the orchestrator asks whether to stop the crew. To stop every station, run:

tares factory crew down

Run tares factory crew up when you have the next project. Tares keeps the projects, tickets and answers, so the crew carries on from them.

What you get

• A clear end point that you set. The project is Done when you say it is, not when a counter reaches a number.
• A record of the finish. Tares stores your words on the project, with every ticket merged.
• A tidy Crew page. The finished project moves to the finished list and the open projects stay in view.
• A full history on the project page. The Tickets fold keeps each pull request and review round. The Decisions fold keeps every question and your answer. The Assumptions fold keeps every choice the crew made and whether you kept it.
• A crew you stop on your own terms. Finishing a project does not stop the stations, and tares factory crew down stops them when you choose.

When something else fits

• If you want to pick up a finished project again, hand it to the crew again, for example with a follow-up spec.
• If you want to know what moved across projects without opening each page, use Standup on the Crew page. It lists what is done, started, in review, blocked and waiting on you.

Related