16 Person-Days of Development Done in 2 Hours — Design Doc Completeness Determines Speed
16 Person-Days Became 2 Hours
Ever sat down with AI hoping for a miracle, only to spend an hour answering its questions?
On a new personal project, I shipped implementation that would normally take 16 person-days by hand, in about 2 hours, using AI-driven development (Claude Code).
This article isn’t a “look how amazing AI is” piece. It’s about how the completeness of a design doc quietly sets the ceiling on development speed.
Why It Finished in 2 Hours
In AI-driven development, AI is excellent at “implementation” and weak at “judgment.”
| Task | AI Ability | Condition |
|---|---|---|
| Writing code | Excellent | If what to write is clear |
| Writing tests | Excellent | If what to test is clear |
| Choosing architecture | Weak | Too many options → hesitation |
| Designing data models | Weak | Needs business rule understanding |
Eliminate “judgment” from AI’s work, and AI runs flat-out.
My DESIGN.md was 3,500 lines across 20 sections. Tech stack, architecture, data models, API endpoints, permissions, screen flows — pre-defined. Everything.
I left AI zero room to think. That’s why it finished in 2 hours.
Vague vs Complete Design Docs
| Aspect | Vague | Complete |
|---|---|---|
| Tech | ”Use React" | "Next.js 15 App Router + Prisma 7 + PostgreSQL 16” |
| Data | ”Users and projects exist” | Full table definitions with columns, types, constraints |
| API | ”Implement CRUD” | Endpoint list with paths, methods, request/response types |
| Permissions | ”Admin and regular users” | RBAC matrix (role × resource × operation) |
Vague docs → AI asks questions at every step. Complete docs → AI just implements.
Design Docs Are “Prepaid Development Time”
| Approach | Design | Implementation | Total |
|---|---|---|---|
| No design | 0 hours | 20 hours (with rework) | 20 hours |
| Design first | 4 hours | 2 hours (no rework) | 6 hours |
Time spent on the design doc isn’t consumption. It’s prepayment.
In Closing
Raising design doc completeness is tedious work. But it’s the only knob that raises the ceiling on development speed.
16 person-days became 2 hours not because AI was fast, but because the design doc didn’t let AI think.
So what exactly do you write to make a “complete” design doc? The next article breaks down the actual 20-section structure.
AI That Implements Without Hesitation — How to Write a 20-Section Design Doc (Published April 25)
Related Articles
- AI That Implements Without Hesitation — How to Write a 20-Section Design Doc — The concrete structure
- “The Testing Phase Disappeared” — AI-Driven vs Traditional Development Compared — AI development performance data
- “Essentialism” and “Effortless” — The Two Wheels of What to Do and How to Do It — The thinking behind “what to do”