ForgeSDLC

ForgeSDLC is a ceremony-driven delivery methodology designed from the ground up for teams that build software alongside AI agents. It replaces heavyweight process with lightweight, high-signal ceremonies — and backs every decision with a body-of-knowledge framework called Blueprints.

Why ForgeSDLC?

Traditional methodologies assumed human–human coordination. The common update is humans assisted by AI—faster hands, but people still carry most of the steering, synthesis, and glue work.

ForgeSDLC is built for the next shift: humans assist AI to orchestrate delivery—from idea shaping through to outcomes. Agents scale production; people own intent, risk, and irreversible decisions so speed stays tied to what should ship.

Core Concepts

Sparks

The atomic unit of work. A Spark maps directly to a task in your WBS — one identity, not two parallel tracking systems. Sparks are completed, not "moved across a board."

Versonas

Discipline challenge agents (AI or human) invoked at decision points. A DevOps Versona stress-tests delivery and reliability; a Testing Versona stress-tests quality evidence and test design. Each Versona draws from the matching discipline blueprint.

Charge

The view of work in progress — not a board, but a lens. Charge shows what's active, what's blocked, and what decisions are pending. It replaces the Kanban board with a decision-oriented view.

The 17 Forge Principles

ForgeSDLC is guided by 17 principles that keep the methodology lean:

1. Do not add process weight that exceeds the waste it prevents
2. Log decisions, not narration
3. Automate journals
4. Versonas at decision points, not everywhere
5. Charge is a view, not a board

See all 17 principles →

Use the Explore ForgeSDLC cards below for curated entry points by tier.