AI Pipelines

Plan Pipeline

Create detailed site build plans from client briefs and brand identity.

Plan Pipeline

The plan pipeline generates a comprehensive build plan document that the build pipeline executes. Planning is document-only — no code, repos, or deploys.

Quick Reference

Field	Value
Trigger	`plan [business name]`
Example	`plan Oakwood Barber Co`
Domain	Client Delivery
Model	3-pass Opus (planner, worker, reviewer)
Requires	Approved brief + brand identity in client folder
Output	Build plan at `knowledge/clients/[business-name]/build-plan.md`
Your time	Review and edit the plan before running `build`

How It Works

Pass 1 — Planner (Opus)

Reads the brief and brand identity from the client folder
Determines tier (Starter/Growth/Premium)
Outlines pages, components, integrations, SEO strategy, and content requirements

Pass 2 — Worker (Opus)

Writes the full build plan draft with client-specific data for every section

Pass 3 — Reviewer (Opus)

Validates tier deliverables match the brief
Ensures all integrations are specified and every page has a full spec
Saves to both the client folder and .output/

Prerequisites

knowledge/clients/[business-name]/brief.md — approved brief
knowledge/clients/[business-name]/brand/ — brand identity (run brand [business] first if missing)

What Happens Next

Review the plan, make any edits, then run build [business] to execute it.

Propose Pipeline

Generate client proposals from completed briefs using tiered model routing.

Build Pipeline

Execute approved build plans across 5 phases with state tracking and verification gates.

On this page

Plan Pipeline Quick Reference How It Works Pass 1 — Planner (Opus)Pass 2 — Worker (Opus)Pass 3 — Reviewer (Opus)Prerequisites What Happens Next