Handbook
Blueprints — adoption, setup, and the engineering handbook
Blueprints is a reusable framework for software-project documentation and process: packaged Markdown you embed in your product repository so teams share the same lifecycle vocabulary, ceremonies, and discipline…
Start here
| I want to… | Open |
|---|---|
| Understand what to adopt and choose a path | Adopting Blueprints |
| Follow guided quickstarts (first hour, hubs) | Quickstarts |
| Run the full ordered checklist | Project setup profile |
| Use Forge Studio next to your repo | Forge Studio quickstart |
| Fix layout, submodule, or Forge issues | Troubleshooting and FAQ |
Choose an adoption path
Blueprints is not one-size-fits-all. Adopting Blueprints describes intent-driven paths (solo, team, organization) so you take the depth you need without boiling the ocean.
First hour in your repo
When you are ready to run commands, use Quickstarts — First hour: submodule, workspace layout, Forge initialization, and editor alignment—about sixty minutes with checks after each step.
Full setup profile
When you want end-to-end standardization in a single checklist, use the Project setup profile. It assumes the same layout as the first-hour flow, with every optional layer spelled out in order.
Forge Studio companion
Forge Studio (in the separate forge-lenses app) sits beside your clones: workspace visibility, plan surfaces, and the Blueprints Wizard for guided sessions. Start with the Forge Studio quickstart. Companion guides for running Lenses and Studio locally live at blueprints.forgesdlc.com/lenses/.
What you get in your repo
- A frozen baseline you update deliberately (submodule pointer and package policy)—so everyone reads the same core text.
- Your project-specific interpretations, directives, and docs at the repository root next to that baseline—where your team’s work actually lives.
- Optional alignment with Forge (artifacts, logs, Versonas) and editor rules—without changing how you ship code.
Companion guides and tools
- Open the handbook — this site is the reader-friendly view of the same Markdown: blueprints.forgesdlc.com.
- Lenses & Forge Studio — local companion app and guides: Lenses hub.
- Shared design system (themes, diagrams) — Design system.
- Short articles — Blog.
Help and troubleshooting
Use the Troubleshooting and FAQ for submodule layout, Forge paths, and common setup mistakes.
Explore more in the handbook
When you need a specific lifecycle or discipline package, browse from the SDLC and PDLC hubs inside the handbook, or open the Automation area for agents and tasklets. Those pages are written for ongoing use—not as a first-day directory map.
Maintainer and contributor resources
Deeper reference (roadmap, design principles, repository layout notes, and change policy) lives only on GitHub in the docs/ tree of the upstream repository. It is not part of the adoption-first reading path on this site.
Blog and community (GitHub): Contributing · Code of conduct · Security · License