Can a crew of Claude Code sessions handle docs updates in a documentation website?

Yes, Tares can run a crew of Claude Code sessions that turns docs updates in a documentation website repo into pull requests merged on main. The orchestrator starts one builder per milestone and repo, and each pull request merges only after the reviewer passes it and CI is green. You plan the work once with tares factory spec, and the crew carries it out.

How it works

The software factory for Claude Code is a crew of sessions running on your machine. A documentation website that lives in a GitHub repo is a repo like any other, so you hand it over the same way as a code project.

• Builder assignment. The orchestrator hands out the work and starts builders, one per milestone and repo of a project, up to the number you allow. If a project spans the docs repo and an application repo, each repo gets its own builder for each milestone.
• One ticket, one branch. Each builder takes a ticket, works on its own branch and opens a pull request.
• The merge bar. The reviewer reviews every pull request to a fixed bar and posts its verdict on it. The builder merges once the reviewer passes it and CI is green. Nothing merges before that.
• Acceptance checks. The plan you agree on contains milestones with acceptance checks, tickets with a working doc each, and an AGENTS.md. The checks for a docs milestone are written there, before any builder starts.
• The record. Tares holds the plan, the tickets and their stages, every review and the assumptions the crew made. If a session restarts, the crew carries on where it stopped.

The crew can also serve several projects at once, so a docs project and a code project can run side by side.

Set it up

Setup follows the Get started guide. For a local Tares, the steps in order are below.

1. Check that Claude Code is signed in, that gh is signed in with write access to the docs repo, and that git, jq and curl are installed.
2. Install the CLI and start Tares locally.
3. In a second terminal, start the MCP endpoint every crew session shares. On Tares Cloud, sign in with tares login instead and skip this step.
4. Give Tares access to GitHub, under Settings > GitHub for a local Tares or with Connect GitHub on Tares Cloud. Tares reads the pull request, CI and merge state of every ticket itself.
5. Bring up the crew.
6. In the docs repo, or a folder that holds its repos, plan the project.

uv tool install tares     # or: brew install glassflow/tap/tares
tares up
tares mcp --transport streamable-http
tares factory crew up
tares factory spec "what you want to build"

The first crew up asks how far the crew may go: whether it merges on its own after review and green CI or waits for your yes, whether it releases, how many builders run at once, and anything you always allow. Describe the docs updates you want in the spec prompt. It interviews you one question at a time, has a second model attack the plan, and writes the project into Tares. Then it asks whether to hand the project to the crew. Say yes and the orchestrator picks it up.

To follow along, run tares factory crew attach orchestrator to answer questions, and tares factory doctor to check that everything the crew needs is in place.

What you get

• Docs updates land as pull requests on main, each from its own branch, one ticket at a time.
• Every pull request carries the reviewer’s verdict, and a builder merges it only when the reviewer has passed it and CI is green.
• Builders are split by milestone and repo, so work across the docs repo and other repos does not queue behind a single session.
• You talk to one session, the orchestrator. Questions come to you one at a time, each with a recommendation.
• The Crew page of the Tares console shows each project’s progress, its builders and the pull requests waiting for review.
• You can make one project wait for your yes before every merge, even when the rest of the crew merges on its own.
• Choices the crew made on its own are written down, so you can check them at the end of each milestone.

When something else fits

• For one small docs change, work in your own Claude Code session with tares factory session. It plans a small project and builds it right there, still on Tares.
• If you want tickets tracked in Linear or GitHub Issues, you can link either to the project. Tares reads them and sessions change them with their own tools.
• The crew is built for solo developers and very small teams on one machine, using your own Claude Code login and your own GitHub repos.

Related