Skip to Content
Cheat Sheet/bootstrap-architecture

/bootstrap-architecture

The second phase of project setup — launches the system-architect agent to translate the PRD into a Technical Architecture document that downstream agents (worker, reviewer, tester) read for context.

When to use it

Run this right after /bootstrap-product has produced the PRD. The system-architect agent reads docs/PRODUCT-REQUIREMENTS.md, asks targeted follow-up questions about technology choices and system boundaries, and drafts docs/TECHNICAL-ARCHITECTURE.md — the canonical reference for what this project’s stack looks like and why. The ticket-worker uses this to make implementation-level decisions consistent with the project’s architecture rather than re-deriving them per ticket.

If you skip this phase, every ticket the worker takes on will surface the same architectural questions (“what database?”, “what auth shape?”, “what deployment target?”) and answer them inconsistently. The architecture doc is the leverage point — one focused session locks in answers that propagate to every subsequent agent invocation.

Don’t run this before the PRD is reasonably stable. Architecture decisions hinge on what the product is and who it serves; without the PRD, the architect agent has nothing concrete to reason about and falls back to generic best practices that may not fit.

How it fits

The architecture doc becomes upstream context for the rest of the setup chain and for ongoing implementation work. Both /create-ticket and /work-ticket read it to populate Environment Context per the ticket format.

What it does (quick)

  • Verifies docs/PRODUCT-REQUIREMENTS.md exists (pre-flight)
  • Launches the system-architect agent with the PRD as context
  • Walks you through architecture decisions: technology stack, system components and boundaries, data models, integration points, non-functional requirements
  • Drafts docs/TECHNICAL-ARCHITECTURE.md capturing the decisions and the rationale behind them
  • Surfaces architectural ambiguities the PRD didn’t pin down — those become open items the operator resolves before /lock-scope

Canonical spec: .claude/commands/bootstrap-architecture.md

Last updated on
/bootstrap-product/bootstrap-agents