How do I write a spec a Claude Code crew can build small features from in a Node/TypeScript app?

Tares writes the spec for you: run tares factory spec in your Node/TypeScript repo and /tares:spec interviews you one question at a time. A second model attacks the plan, and the result lands in a Tares project as a spec, milestones with acceptance checks, tickets with a working doc each, and an AGENTS.md. You then hand the project to the Claude Code crew, which builds the tickets into pull requests merged on main.

How it works

You do not draft the spec by hand. You describe the feature in a sentence and answer the interview.

• The interview. /tares:spec asks one question at a time, so each answer shapes the next question.
• The attack. A second model attacks the plan before it is written down, so weak points surface while they are still cheap to fix.
• What lands in Tares. The plan becomes a Tares project with four parts: the spec, milestones with acceptance checks, tickets with a working doc each, and an AGENTS.md.
• The hand-over. The interview ends by asking whether to hand the project to the crew. If you say yes, the orchestrator picks it up.

The crew is an orchestrator, a reviewer and builders, each a Claude Code session on your machine. Builders are started one per milestone and repo. Each takes a ticket, works on its own branch and opens a pull request. It merges once the reviewer passes it and CI is green. The reviewer holds every pull request to a fixed bar. Tares keeps the plan, tickets, reviews and your answers, so a crew that restarts carries on where it stopped.

For a Node/TypeScript app, the crew’s search tooling matters too. tares factory doctor finds TypeScript through tsconfig.json and JavaScript through package.json. It checks whether Claude Code has a language server for them, so builders and the reviewer can look up definitions, references and callers.

Set it up

1. Check that Claude Code is signed in, gh is signed in with write access to your repo, and git, jq and curl are installed.
2. Install the CLI and start Tares locally. On Tares Cloud, run tares login instead and pick your workspace in the browser.
3. On a local Tares, start the MCP endpoint in a second terminal. Crew sessions reach Tares only through it.
4. Give Tares access to GitHub. Use Settings > GitHub on a local Tares, or Connect GitHub on Tares Cloud.
5. Bring up the crew. The first run asks how far it may go: whether it merges on its own after review and green CI or waits for your yes, whether it releases, whether a second model checks every commit, and how many builders run at once.
6. Optional for Node/TypeScript: if crew up lists a missing language server, say yes to install it. The TypeScript server comes from npm install -g typescript-language-server typescript, then claude plugin install typescript-lsp@claude-plugins-official.
7. From inside your app’s repo, start the spec with the feature you want.

gh auth login
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"

8. Answer the questions. Each one is a single question, so name the one feature you want and answer in your own words. Your answers are kept on Tares in those words.
9. If you want the tickets in GitHub Issues, say so during /tares:spec and name the repo. Claude creates the issues with gh and links them. Run gh auth login --scopes repo first. Linear works as a ticket home too, linked from the project’s Tickets page.
10. Say yes when asked to hand the project to the crew, then run tares factory crew attach orchestrator to answer its questions.

The Get started page has the full walkthrough and the commands table.

What you get

• A Tares project built from your interview: a spec, milestones with acceptance checks, tickets with a working doc each, and an AGENTS.md.
• A plan that a second model has already attacked, before any builder writes code.
• Pull requests from builders, each reviewed to a fixed bar and merged on main once CI is green.
• Questions that reach you in the orchestrator’s session one at a time, each with a recommendation. The Crew page in the console shows progress and the question waiting for you.
• A written record of every assumption the crew made on its own, so you check it at the end of each milestone instead of during every step.
• A restartable crew, because the plan, tickets and your answers stay on Tares.

When something else fits

• If the idea is small enough to build in one sitting, run tares factory session with your idea. You get a few questions, a short spec and a ticket list on Tares, and your own Claude Code session builds it.
• If a project is already planned, tares factory session followed by the project name works its ready tickets in your session, with no crew needed.

Related