70 The Crux of prd2code is That Requirements Are Too Specific

70 The Crux of prd2code is That Requirements Are Too Specific Looking at it in reverse, the thinking suddenly becomes clear

All along, we've been thinking forward: High-quality input => AI => High-quality output

High-quality means covering every detail, clear and explicit, even requiring that once output it can't be changed anymore, changing it belongs to the next requirement

Always want to require product to output a standard high-quality product document, then throw it to AI, as one of the necessary conditions for high-quality code output

But, when things reach this step it's almost impossible to implement, stuck here

Yesterday suddenly thinking, the requirement granularity I give to AI is getting larger and larger, time spent on requirement clarification is increasing, going against the above approach