What is ForgeSDLC?
ForgeSDLC is a software delivery methodology designed for teams that build software alongside AI agents. It combines three elements:
- A discipline-challenge layer — lightweight, decision-focused Versonas (discipline challenge agents) invoked when stakes warrant
- A body-of-knowledge system — reusable discipline blueprints that encode engineering best practices
- A lean process philosophy — 17 principles that prevent process bloat
How it works
flowchart LR
S[Spark created] --> W[Work begins]
W --> B{Versona needed?}
B -->|Yes| C[Apply discipline knowledge]
C --> D[Decision made]
D --> W
B -->|No| E[Spark completed]
E --> V[Charge view updated]
The work cycle
- A Spark is created — the atomic work unit, mapped 1:1 to your WBS task hierarchy
- Work proceeds — humans and AI agents collaborate on the Spark
- When a decision point arises, relevant Versonas are invoked — applying the discipline's body of knowledge
- The decision is logged, the journal updates automatically, and work continues
- When the Spark completes, the Charge view reflects the new state
No overhead when none is needed
The key insight: not every task needs a Versona. A straightforward code change doesn't need a DevOps Versona. But a deployment architecture decision does. ForgeSDLC applies process where it matters and stays out of the way everywhere else.
Core vocabulary
| Term | Meaning |
|---|---|
| Spark | The atomic unit of work. Maps 1:1 to a WBS task. One identity — not a "ticket" and a "task" separately. |
| Versonas | Discipline challenge agents (often AI) that apply discipline-specific knowledge at a decision point. |
| Charge | The live view of work state. Not a Kanban board — a decision-oriented lens on what's active, blocked, or pending review. |
| Blueprint | A reusable package of policies, templates, and bodies of knowledge for a specific discipline (DevOps, Testing, Architecture, etc.). |
| Forge Principles | 17 guiding principles that keep the methodology lean and decision-focused. |
Who is ForgeSDLC for?
- Teams using AI coding assistants (Cursor, Copilot, Windsurf) who find that traditional ceremonies don't account for AI-generated output
- Engineering leaders looking for a methodology that scales without adding process weight
- Startups and scale-ups that want structure without bureaucracy
- Enterprise teams transitioning from heavyweight frameworks (SAFe, PRINCE2) to something leaner
How ForgeSDLC relates to Blueprints
ForgeSDLC is a methodology. Blueprints are the engineering framework that powers it. You can use Blueprints without ForgeSDLC (they work with any methodology). But when combined, the ceremony structure maps directly to blueprint areas — each Versona knows which body of knowledge to apply because the blueprint defines it.