Manual-Driven Development: A Method to Prevent Claude Code's Confident Divergence

Manual-Driven Development (MDD) is a methodology designed to solve confident divergence in Claude Code, where the AI produces incorrect code that compiles and passes its own tests because it's working from incorrect assumptions about the system.

The Problem: Confident Divergence

When Claude Code works on large production codebases, it reads a few files, infers patterns, and starts coding based on assumptions. This leads to confident divergence - code that looks correct, runs, passes tests, but is wrong because Claude wrote tests against its assumptions rather than the actual system behavior. The divergence only surfaces in production when real users hit edge cases Claude never knew existed.

The author notes this isn't just about Claude not knowing your system - it's that developers can't reliably narrate their entire system either. At 11pm, you won't remember to mention that operators are scoped to specific groups, that ROLE_HIERARCHY is defined in three different files, or that base-tier policies are system-only and cannot be created via the API.

MDD Results in Production

In a production audit using MDD:

• Seven sections audited
• 190 findings identified
• 876 new tests written
• 7 hours and 48 minutes of Claude Code session time
• Estimated 234 to 361 hours of human developer time saved (30-46x compression ratio)
• Zero CLAUDE.md rule violations across all sections

The codebase had 200+ routes, 80+ models, and a daemon enforcement pipeline that converts network policies into live nftables rules on the host.

How MDD Differs from Other Tools

MDD addresses a different problem than existing tools:

• GSD solves context rot (quality degradation as sessions fill up)
• Mem0 and Claude-Mem solve session amnesia (forgetting everything when sessions end)
• MDD solves confident divergence (wrong code based on incorrect assumptions)

All three can run together without conflict. RuleCatch, which monitors rule enforcement in real time, reported 60% fewer rule violations during the SwarmK build with MDD compared to sessions without MDD - same model, same rules, same codebase.

The methodology, prompts, and section-by-section data are documented and reproducible according to the source.