Getting started with Forge SDLC

What you already have

• Methodology and process — See blueprints.forgesdlc.com for the engineering handbook (SDLC, PDLC, disciplines, agents).
• Product and encyclopedia — forgesdlc.com explains the approach in business terms and hosts deeper knowledge articles.

Practical first steps

1. Align on intent — Decide what “done” means for your next slice of work (outcome, constraints, who approves).
2. Put policy in-repo — Prefer small, reviewable docs and checklists beside the code they govern.
3. Use agents for execution, humans for judgment — Automate repetition; keep sign-off and trade-offs with people.
4. Roadmap before deep WBS — If you use the Forge Product Manager path, draft the roadmap first, apply Definition of Ready (outcome, evidence, horizon, OKR fit, dependencies, non-goals, next gate), then run Product Management Versona and follow Suggested next Versonas before breaking work into a heavy WBS. Hub: Forge Product Manager (orchestration vs challenge-only Versona); full handbook copy lives in blueprints.

Terminology and lifecycle maps

On the same site (generated methodology pages), use these when you need definitions or a phase-by-phase view from problem discovery through delivery:

• Forge naming reference — table of Forge terms (Product Spark vs Forge Spark, Ore, Ingot, Charge, …) and where each is documented in blueprints.
• Forge ↔ SDLC ↔ PDLC bridge — alignment of Forge mechanics to SDLC A–F and PDLC P1–P6.
• Product creation → delivery (IPE map) — Inputs → Process → Outputs by phase, with industry vs Forge language and example discipline Sparks.

Shorter hub: Terminology and lifecycle (tutorial index page).

How these pages are built: Documentation sites and Kitchen Sink — forge-autodoc, handbook_page, and the blueprints handbook generator.

Next

Add more tutorials alongside this file under tutorials/ in the forgesdlc repository; the site build turns them into HTML under /tutorials/ on the deployed site. See Documentation sites and Kitchen Sink for the pipeline.