liquizzz

Crewbook Build — Testing skill for Claude Code

Testing community

You bring the idea.

How to install Crewbook Build

This entry records only its repository, not the path inside it, so there is no exact command to give. Open liquizzz/crewbook-build and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Crewbook Build does

You bring the idea. Your AI team ships the software. Crewbook: Build sets up a Claude Code agent team (PO, Lead, Dev) with spec-driven gates you approve, so anyone can build high-quality software from zero, coding or not.

Alternatives in Testing

Cc Sdd — Spec-driven development (SDD) for your team's workflow 3.1k ★
Factory — Dark Factory Mode - Spec-in, software-out autonomous pipeline 2.8k ★
Spec Kitty — Spec-Driven Development for serious software developers 1.6k ★

README

Crewbook: Build

**You bring the idea. Your AI team ships the software.**

A step-by-step Claude Code playbook and starter kit for building high-quality software from zero, whether you have written code for years or never written a line. You lead a crew of Claude Code sessions (PO, Lead, Dev) the way you would lead a real team, and nothing moves forward until you approve it. One command sets up your project. From then on every session knows its role, picks the right skill for each task, asks you only what it needs and keeps token use down.

Crewbook: Build is the first playbook in the Crewbook series.

**[Start a project in 5 minutes: How to run](HOW-TO-RUN.md)** (once Claude Code, Git, Node.js, Docker and the GitHub CLI are installed)

git clone https://github.com/liquizzz/crewbook-build.git

node crewbook-build/kit/init.mjs

The first time, install the tools listed in How to run (once per machine). Then answer eight short questions (Enter takes each suggestion) and open the `START-HERE.md` it writes into your project. Every next step there is one short command to type, such as `/setup`, `/next `, `/build try`, `/build done` or `/release`, and each hand-off ends with a prompt you copy with one click.

What you get: a Claude Code agent team in one command

You get	How
A ready project in one command	`init.mjs` creates the folder, git branches, the Lead's worktree (its own folder of the project, one per session), the GitHub repo (private or public) with labels and a kanban board, CI and Docker image builds, the Claude Code plugins the team uses, and `START-HERE.md`; the Lead's `/setup` then opens the gate issues and the other roles' worktrees
A small team that knows its job	Every project starts with three sessions: PO (your requests), Lead (design, stack, review, release) and one Dev. Test, UI/UX and DevOps join only for high-stakes work. Each role has a role file with its rules and paths; a guard hook