What will the crew ask me while it works on docs updates?
Tares asks you two kinds of questions while the crew works: steps only you can take on your machine, and a keep-or-change question at the end of each milestone. You answer them in the orchestrator’s session, and each answer is recorded on the project page. The same questions apply to a docs updates project as to any project you hand to the crew.
How it works
The crew asks only what it cannot settle itself. Everything else it decides, writes down and carries on.
Steps only you can take. Some things can only happen on your machine. In the project followed on A project, end to end, the crew asked for two:
- Trust the repo folder in Claude Code once, so the builder can start.
- Give Tares a GitHub token, so it can read pull request, CI and merge state.
Questions at the end of each milestone. When the crew meets something the plan does not cover, it picks the sensible answer, records it as an assumption and keeps going. At the end of each milestone the orchestrator brings you all of that milestone’s 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.
A few other prompts can reach you:
- A station that asks for a permission, a prompt or an answer shows as Waiting for you and stays stopped until you reply.
- If you chose to approve merges yourself, you answer a merge approval before each merge.
- After the last milestone, the orchestrator asks whether the project is finished.
- With no project left, it asks whether to stop the crew.
You answer all of these in the orchestrator’s session. The answer goes into the project’s Decisions fold as you typed it, up to 4,000 characters. A long pasted reply with several lines or paragraphs is matched in full.
Set it up
-
Bring up the crew and plan the work. If you have not set up the software factory yet, start with Get started.
tares factory crew up tares factory spec "what you want to build" -
Say yes when the spec session asks whether to hand the project to the crew. The orchestrator picks it up and starts a builder for the first milestone.
-
Open the orchestrator’s session in your terminal and keep it handy. Questions arrive there.
-
Answer the one-time machine steps when they come: trust the repo folder, and give Tares a GitHub token.
-
At the end of each milestone, read the assumptions and say which you keep. To make an answer stand from now on, say so, for this project or for every project.
-
Watch for waiting questions on the Crew page, at
http://127.0.0.1:8787/crewlocally. Questions waiting for you appear at the top, and the project page lists them under questions waiting for you. -
If a station goes quiet, bring it back:
tares factory crew watch
What you get
- A short list of questions instead of constant interruptions. In the sample project the crew went from a spec to eight merged pull requests in about three hours and asked five questions.
- A clear split. You handle what only you can do on your machine, and you review the crew’s own choices in batches at milestone boundaries.
- A record of everything. The Decisions fold holds every question the crew asked and your answer in your own words, newest first. The Assumptions fold holds every choice the crew made on its own and whether you kept it.
- Control over what stands. Your answer can apply to one project or to every project.
- A clean finish. After the last milestone you confirm the project is done, and Tares marks it Done with your words and moves it to the finished list.
When something else fits
- If a builder holding a ticket shows a notice that it is waiting for you, open its session in a terminal and answer there, or say “continue”. You can also talk to the orchestrator to steer the work.
- A station shown as Idle needs nothing from you. It is waiting on its own Monitor or a peer and resumes by itself.
- For an overview instead of questions, open Standup on the Crew page. It lists what is done, in review, blocked and waiting on you.