Inception
Requirements, user stories and workflow planning turn a raw request into a plan. Nothing generates until a human signs it.
SpecForge merges GitHub Spec Kit with AWS AI-DLC. No agent touches a file until a human signs the spec and the plan.

Spec Kit supplies the specs and AI-DLC supplies the discipline. SpecForge runs both on every build, not only when someone remembers to be careful.
Claude Code runs a PreToolUse hook, a check that fires before any tool touches a file. If a human has not approved the spec and plan, the edit never happens.
Every build runs three phases in order. A human signs off before each move to the next.
Requirements, user stories and workflow planning turn a raw request into a plan. Nothing generates until a human signs it.
Agents write the code here. AIDLC, my eight-phase build engine, runs every change through evals before it ships.
Read the AIDLC guideDeployment, monitoring and the audit trail carry the system past launch. Then your team owns and runs it without me.
Once you approve the plan, SpecForge can run the steps on its own. I call that the Ralph loop. It never adds a step you did not approve.
SpecForge first documents the architecture and business logic already in production. Every approval and code change after that lands in an audit trail that ships with the repo.
SpecForge and AIDLC run on a few words that mean something specific here. Each one has its own post.
SpecForge is open source. Install it from GitHub, or read the AIDLC guide for the eight phases it runs.