Sixteen steps, each with a clear deliverable. Skip any one, and the debt comes due somewhere downstream.
After reading, you can answer
一个想法到上线，中间到底要经过什么
每一步该交出什么东西，下一步才能开工
AI 真正压缩掉的是哪几步，哪几步一步没少
This workflow was forged by large-team coordination, not ceremony. Its value is that it fixes the deliverables: if the previous step produces nothing, the next step can't start. When you build alone, the headcount drops but the deliverables don't—they just move from documents into judgment calls in your head.
What each of the four phases delivers
The form changes; the questions don't. A spec still answers the same questions a use-case document used to: what entities exist, what states can occur, how exceptions are handled.
Which steps AI compresses
Re-rank the sixteen steps by "how much can AI do for you," and you'll see where your time should go.
The form changes; the questions don't. A spec still answers the same questions a use-case document used to: what entities exist, what states can occur, how exceptions are handled.
This explains a common feeling: the faster you build, the more you throw away. Output speed went up tenfold; judgment speed didn't.
How one person runs it
Compress sixteen steps into five. Keep the deliverables; swap the form from documents into something you can feed straight to AI.
The form changes; the questions don't. A spec still answers the same questions a use-case document used to: what entities exist, what states can occur, how exceptions are handled.
