Skip to Content

What will the crew ask me while it works on framework migrations?

Tares has the crew ask you two kinds of questions: steps only you can take on your machine, and a question at the end of each milestone about whether to keep the choices the crew made on its own. You answer both in the orchestrator’s session. Every answer is recorded on the project page, so you can see later what you decided.

How it works

The software factory for Claude Code asks the same two kinds of questions on any project you hand it, including a framework migration. The Get started page covers the basics, and A project, end to end follows one project through all of them.

1. Steps only you can take on your machine. The crew cannot do these for you. In the worked example, the crew asked the person to:

  • trust the repo folder in Claude Code once, so the builder could start
  • give Tares a GitHub token, so it could read pull request, CI and merge state

2. A question at the end of each milestone. When the crew meets something the plan does not cover, it picks the sensible answer, writes it down as an assumption and carries on. At the end of each milestone, the orchestrator brings you its assumptions in one question: do you keep the choices the crew made on its own? Each assumption names the tickets it touches and the builder that made it.

In the worked example, one assumption was a config file name: the working doc named vitest.config.ts, which failed to load on the repo’s Node version, so the builder used vitest.config.mts. Another was leaving existing production data alone and flagging it in the pull request. Expect assumptions of that size, a small choice the plan did not settle, written down for you to keep or change.

Where you answer. You answer in the orchestrator’s session. Your answer goes into the Decisions fold as you typed it, up to 4,000 characters. Long pasted replies with several lines or paragraphs are matched in full. To make an answer stand from now on, say so, for this project or for every project.

When a station needs you. If a builder asks for a permission, a prompt or an answer, it shows as Waiting for you and stays stopped until you reply. Open its session in a terminal and answer there, or say “continue”. The orchestrator answers the builders itself and brings you only what needs you, as a question in its session.

If you chose at crew up that the crew waits for your yes before every merge, merge approvals show up as questions too, each recorded with your answer.

Set it up

  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, start Tares locally and, in a second terminal, start the MCP endpoint every crew session shares. On Tares Cloud, run tares login instead and skip the MCP step.
  3. Bring up the crew, then plan the migration as a project.
tares up
tares mcp --transport streamable-http
tares factory crew up
tares factory spec "what you want to build"
  1. Answer Claude Code’s questions in the spec session, then say yes to handing the project to the crew. The orchestrator picks it up and starts a builder for the first milestone.
  2. Watch for questions. Open the Crew page in the console (http://127.0.0.1:8787/crew locally). Questions waiting for you appear at the top. The project page lists them too, under questions waiting for you.
  3. Answer in the orchestrator’s session. At the end of each milestone, say whether you keep the assumptions it lists.
  4. If a station goes Quiet, run tares factory crew watch to bring it back.

What you get

  • You take only the steps that need your machine, and the crew handles the rest.
  • You review the crew’s own choices once per milestone, in one question, instead of being asked at every turn.
  • The Decisions fold keeps every question the crew asked and your answer in your own words, newest first.
  • The Assumptions fold keeps every choice the crew made on its own and whether you kept it.
  • Your standing answers apply to this project or to every project, as you say.
  • When the last milestone is done, the orchestrator asks whether the project is finished. Your answer marks it Done, with every ticket merged.

When something else fits

  • To steer the work mid-build, talk to the orchestrator rather than waiting for a question.
  • When a station shows Idle, it needs nothing from you and resumes by itself, so you have nothing to answer.
  • When no project is left, the orchestrator asks whether to stop the crew. Run tares factory crew down to stop every station.

Still stuck? Get help

Last updated on