ddd-guide

Document-driven development treats documentation as the single source of truth for evolving codebases, capturing requirements and designs before coding to ensure AI-driven updates stay aligned with human intent.

To prevent context poisoning, you enforce a single source of truth, reduce documentation duplication, and resolve terminology conflicts before implementation through a phase-driven methodology.

You plan new features by starting with Phase 0 planning to align goals, then updating documentation in Phase 1 before moving through implementation planning, coding, and verification with human gates.

Yes, you can retcon documentation for existing codebases by systematically orchestrating updates with human gates to ensure progressive organization and prevent drift during code evolution.

Yes, a doc-first workflow works for progressive organization by structuring documents to reveal complexity gradually, which enables easier onboarding and maintenance across the codebase.

The limitation is the strict overhead of a six-phase process requiring human gates at every step, which may slow down rapid prototyping but guarantees auditable outcomes and prevents context poisoning.