Handbook

Project setup checklist for Blueprints in a consuming repository

The full ordered checklist for a product repository that hosts blueprints/ at the repository root (typically a git submodule): submodule through optional Forge and product-led flows, with the same assumptions as the…

What it is

The full ordered checklist for a product repository that hosts blueprints/ at the repository root (typically a git submodule): submodule through optional Forge and product-led flows, with the same assumptions as the first-hour quickstart, but in one place.

Handbook-first: every command and relative path below assumes your shell’s current working directory is the consuming repository root — the folder that will list blueprints/, sdlc/, forge/, and (after Bootstrap) your project docs. That matches the first-hour quickstart and keeps one canonical story for where scripts run.

Terms (quick read)

Term Plain language
Blueprints Software delivery documentation framework in your repo (often a blueprints/ submodule).
Project setup checklist This profile — ordered steps from submodule through Forge, Cursor, and optional product flows.
Forge Studio Local engineering workspace dashboard (Lenses) for visibility across repos — optional; see Forge Studio quickstart.
Wizard Guided project planning workflow inside Studio — optional.
Versona Discipline lens for structured reviews in Forge — see Versona catalog.

You may copy this file to your project root as SETUP.md if you want a local checklist.

Field Value
Profile version 1.0
Last reviewed 2025-03-24
Blueprints submodule Record git rev-parse HEAD inside blueprints/ after git submodule update

Layout reference: full consuming-repo doc tree (optional detail) — Documentation structure in this handbook.

Setup phases (map of the numbered steps)

Phase Steps Page
Bootstrap 1–3 Setup profile — Bootstrap
Forge + Cursor + automation 4–11 Setup profile — Forge and Cursor
Product-led (optional) 12 Setup profile — Optional product-led

Depth profiles: Minimum = Bootstrap + Forge through a working forge.config.yaml. Recommended = through step 10 (sync-forge-cursor-rules.sh check clean). Full = all rows including optional product-led flows.

Setup phases (visual)

Project setup profile — Bootstrap, then Forge and Cursor, then optional product-led steps

When to use it

Use this page when you are standardizing setup end-to-end after you already know you will use Blueprints at the repo root.

Before you start: if you have not chosen an adoption story yet, skim Adopting Blueprints. For a faster guided pass with verification after each step, use Quickstarts — First hour first, then return here for anything you skipped.

Prerequisites

  • blueprints/ must sit at the repository root next to forge/, sdlc/, docs/, etc. Stock Forge init and tasklet install scripts live under the Blueprints tree and assume you run them from the repo root (paths start with blueprints/). Details: Setup profile — Forge and Cursor.
  • If your org cannot use that layout, you need wrapper scripts or forks that adjust paths — the stock blueprints tooling does not support a configurable BLUEPRINTS_ROOT.

Steps (by phase)

Follow the three pages in order (or jump to the phase you skipped after first hour):

  1. Bootstrap — steps 1–3
  2. Forge and Cursor — steps 4–11
  3. Optional product-led — step 12

How to verify success

  • After Bootstrap: test -f blueprints/sdlc/README.md from repo root; project sdlc/README.md exists.
  • After Forge and Cursor: sync-forge-cursor-rules.sh check passes when you use the recommended preset (if applicable).
  • After optional product-led: artifacts per the linked methodology docs.

What to do next