Good question! It serves as a bootstrap for each module design file (effectively a deeper expansion of what is defined in the PRD). Once you have (at least) design files for each module, PRD is no longer necessary. It usually ends up being inaccurate after the brainstorming phases, which change fundamental bits of the wiring that the initial brainstorm wouldn't cover.
Thanks for sharing this insights. I'm currently leaning heavily into using superpowers as well, so your article was particulary interesting to me.
In your workflow, what happens to the `PRD.md` after the initial module planning phase?
Is it mainly used to guide the decomposition into modules, or does it continue to play a role during implementation?
I might have missed it, but I'm curious wether it's just a planning artifact or an active part of the coding loop.
Good question! It serves as a bootstrap for each module design file (effectively a deeper expansion of what is defined in the PRD). Once you have (at least) design files for each module, PRD is no longer necessary. It usually ends up being inaccurate after the brainstorming phases, which change fundamental bits of the wiring that the initial brainstorm wouldn't cover.