Handbook
Fast setup and adoption paths
This page is the entry to quickstarts: short guided paths with verification. Read the first paragraph under What it is, then use Selection matrix to pick a path.
What it is
The fastest path from “Blueprints is in my repo” to verified progress — commands and checks, not a methodology tour.
Terms (quick read)
| Term | Plain language |
|---|---|
| Blueprints | Software delivery documentation framework at repo root (blueprints/). |
| Forge Studio | Local engineering workspace dashboard (Lenses) — optional companion to this handbook. |
| Wizard | Guided planning workflow inside Studio. |
When to use it
Use this hub when you are ready to run scripts at the repository root next to blueprints/. If you are still choosing how much process to adopt, read Adopting Blueprints first.
Prerequisites
- Git and bash
- Python 3 (Forge init and Cursor rule sync)
- A checkout where
blueprints/can live at the repo root (see Project setup checklist)
Selection matrix
| Quickstart | Time (typical) | Outcome | Prerequisite |
|---|---|---|---|
| First hour | ~60 min | Submodule, project sdlc/, Forge, Cursor rules — verify after each step |
Repo root layout decided |
| Forge Studio | ~30–45 min after tooling | Local forge-lenses server and /studio/ UI |
Git + Python venv; optional after first hour |
| Project setup profile | Multi-session | Full ordered checklist including optional product-led steps | Same root layout; use after first hour or instead of ad hoc steps |
Who starts where
| You are… | Start with |
|---|---|
| Choosing how much to adopt (role / org size) | Adopting Blueprints |
| Ready to run commands today | First hour |
| Standardizing setup for a team or template repo | Project setup profile |
| Wanting Lenses / Studio / Wizard on your machine | Forge Studio after your product repo baseline works |
Quickstart flow (visual)
Steps
Pick one quickstart and follow it end-to-end:
| Quickstart | Outcome |
|---|---|
| First hour in your repo | blueprints/ present, project sdlc/ workspace, minimal Forge layout, Cursor rules — verification after each step |
| Forge Studio | Optional forge-lenses clone or submodule, local server, /studio/ UI — companion product, not inside blueprints/ |
How this hub fits nearby guides
| If you need… | Use |
|---|---|
| Which adoption story fits your role (solo / team / org) | Adopting Blueprints first |
| Verified commands only, ~1 hour | First hour above |
| Full checklist (submodule through optional product flows) | Project setup profile |
| Something failed | Troubleshooting and FAQ |
How to verify success
You completed the chosen quickstart’s Verify / How to verify success section (see that page) without skipping checks you care about for your team.
What to do next
- Adopting Blueprints — ICP-style paths when role context matters
- Project setup profile — full ordered checklist beyond the first hour
- Troubleshooting and FAQ — submodule, paths, Forge/Cursor
Deeper reference (not step 1): Software delivery overview, PDLC, disciplines hub — use after your baseline layout works.