How is the Paper-First Method different from spec-driven development?
They agree on the main point: an AI coding tool should build from a written plan, not from a loose chat. The differences are in what comes before the spec and who writes the first draft.
In a typical spec-driven workflow, you describe the feature, the AI drafts requirements, a design and a task list, and you review and edit them before it builds. In the Paper-First Method, you draw the product by hand, make the AI argue with it, decide the architecture and stack yourself, and only then ask Claude to write the brief, the PRD and the build prompts.
| Spec-driven development | Paper-First Method | |
|---|---|---|
| Starting point | A written description of the feature | One page drawn by hand |
| First draft of the plan | Often written by the AI, reviewed by you | Drawn by you, challenged by the AI |
| Pushback on the idea | Depends on how you prompt | Built in: five questions in step 2 |
| Architecture and stack | Usually proposed inside the spec | Decided by you in steps 3 and 4, before the spec |
| Core document | Requirements, design and tasks | A six-line brief, then a PRD and build prompts as needed |
| Human approval points | Wherever the spec puts them | Drawn first, as the hand on the page |
| Tools | Any coding agent; some tools build it in | Any tools; Sohaib uses Claude, Cursor and Claude Code |
| Best for | Features in a known codebase with clear requirements | New products, unsettled requirements, AI that makes decisions |
When is spec-driven development the right choice?
- The product already exists and you're adding a feature with clear requirements.
- The team has conventions, and the spec's job is to keep the AI inside them.
- The requirements come from someone else, already written.
- You want a reviewable record of requirements, design and tasks for each change.
When should I use the Paper-First Method instead?
- You're starting a new product and its shape isn't settled.
- The hardest question is what to build, not how.
- The AI is part of the product, and you need to decide where a human approves.
- You want the AI to challenge the idea before it helps document it.
Can I use both together?
Yes, and they fit well. Steps 1 to 4 decide what the product is. Step 5 is where a spec-driven workflow can take over: the page, the architecture and the six-line brief become the input to whatever spec format your tool uses.
In the JobFuture build, step 5 produced a PRD with seventeen build prompts inside it. That is a spec. It just came after the paper and the pushback.
Is the Paper-First Method a kind of spec-driven development?
You could see it that way, since it ends in a spec. The difference is emphasis. Spec-driven development focuses on the quality of the spec. The Paper-First Method focuses on the quality of the thinking before the spec, and on keeping the load-bearing decisions (the flow, where a human approves, the architecture and the stack) with a person.