Getting Started

1 Install Braddock in your project

Run inside any existing project directory:

# install in current directory
npx @vitorbritto/braddock init

# or specify a path
npx @vitorbritto/braddock init /path/to/your/project

Braddock scaffolds a .braddock/ and .claude/ folder. Existing files are never overwritten.

2 Define your product vision

Open .braddock/memory/vision.md and describe what you're building. One paragraph is enough. Without this file, the squad has no mission.

Tip: Be specific. The vision feeds the PRD, which feeds the spec, which feeds the code. Vague input = vague output.

3 Fire up the squad in Claude Code

Open Claude Code in your project, paste the content of .braddock/PROMPT.md and hit enter. That's it — the squad initializes itself and runs the pipeline from there.

You are operating inside a virtual squad system called Braddock. Read first, in this order: - .claude/CLAUDE.md - .braddock/memory/vision.md - .braddock/memory/status.md Your mission is to initialize the project and prepare the squad for execution. Rules that cannot be broken: - Never skip steps in the pipeline - Never implement code before an approved PRD and spec exist - Never assume a business rule without recording it in .braddock/memory/decisions.md - Always maintain traceability: vision → PRD → spec → task → code Default pipeline: /kickoff → /create-prd → /create-spec → /breakdown-work → /implement-task → /review-delivery Start now with /kickoff.

From there, each skill points to the next when it finishes. The squad is self-guided.

Pipeline

No mission starts in the middle. Each step produces an artifact that feeds the next.

/kickoff

Initializes the operation and prepares the ground.

→ operation context

/create-prd

PM defines the mission objective and success criteria.

→ PRD.md

/create-spec

Tech Lead, Architect, and UI/UX translate the PRD into a technical plan.

→ SPEC.md

/breakdown-work

Planner decomposes the spec into epics, stories, and small bets.

→ TASKS.md

/implement-task

Executes the next eligible task in the queue.

→ code

/review-delivery

QA and Tech Lead validate what was delivered against the spec.

→ review report

The Squad

Each agent has a fixed role and never acts outside it.

Agent	Role
`pm`	Transforms vision into PRD
`tech-lead`	Architecture, trade-offs, risks
`architect-specialist`	Structure, modules, boundaries
`backend-senior`	Implements business rules
`frontend-senior`	Interface, flows, integration
`ui-ux`	Experience, clarity, conversion
`planner`	Breaks work into epics and tasks
`qa`	Validates, flags gaps, reviews

Getting Started

1 Install Braddock in your project

2 Define your product vision

3 Fire up the squad in Claude Code

Pipeline

The Squad

Code of Honor