Skip to Content

How do I know a project made of framework migrations is finished?

Tares marks a project Done when you tell the orchestrator it is finished. After the last milestone, the orchestrator asks whether the project is finished. When you answer that it is done, Tares records the project as 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 you hand to the software factory for Claude Code has a page of its own, and that page shows where the project stands. If you are new to the factory, start with Get started.

  • Four steps across the top. The project page shows Spec, Build, Review and Done, with a progress bar that has one segment per ticket. For a project of framework migrations, each ticket you planned is one segment.
  • Milestones with acceptance checks. The spec session splits the project into milestones, and each milestone carries its own acceptance checks. The Tickets fold shows each ticket with the builder that held it, its pull request and its review rounds.
  • Assumptions at each milestone. When the crew meets something the plan did not cover, it picks a sensible answer, writes it down as an assumption and carries on. At the end of each milestone, the orchestrator brings you those assumptions in one question, and you say which to keep.
  • The finished question. After the last milestone, the orchestrator asks whether the project is finished. You decide what finished means for your project. In the worked example in A project, end to end, the person deployed the result first and then answered that it was fully deployed, working and done.
  • Done is recorded with your words. Tares marks the project Done with your answer, every ticket merged, and moves it to the finished list on the Crew page. The Decisions fold keeps your answer as you typed it, up to 4,000 characters.

Set it up

  1. Open the project page and watch the progress bar. Each ticket turns into a segment as its pull request merges. A blocked ticket names the tickets it waits for.
  2. At the end of each milestone, answer the orchestrator’s question about the assumptions the crew made. Say yes to the ones you keep. To make an answer stand from now on, say so, for this project or for every project.
  3. Check the outcome yourself, for example by deploying it and confirming it works. The orchestrator asks the finished question only after the last milestone.
  4. Answer the orchestrator’s question in its session with plain words, for example that it is deployed, working and done. Tares marks the project Done with those words.
  5. Open the Crew page in the console (http://127.0.0.1:8787/crew locally). The project now sits in the finished list, folded below the open projects. The project page shows Done and your answer sits in the Decisions fold.
  6. With no project left, the orchestrator asks whether to stop the crew. Stop every station with this command:
tares factory crew down

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

What you get

  • A clear end state. A project is finished when you say so, and the project page and the Crew page both show it as Done.
  • Your words on the record. The project is marked Done with your own answer, and the same answer sits in the Decisions fold beside every other question the crew asked you.
  • A tidy Crew page. Finished projects fold away below the open ones, so the Projects list shows what the crew is still working on.
  • A full history. Every ticket, pull request, review round, decision and assumption stays on the project page after the project is Done.
  • Control over the crew. Marking a project Done does not stop the crew. You choose when to run tares factory crew down.

When something else fits

  • If the work is not finished, say so when the orchestrator asks. To pick up a finished project again later, hand it to the crew again, for example with a follow-up spec.
  • If a station looks stuck while you wait for the last milestone, check its state on the Crew page. A Quiet station is brought back by tares factory crew watch.
  • If more projects are coming, leave the crew running and skip tares factory crew down until you are done for a while.

Still stuck? Get help

Last updated on