This is the most specific feedback in this thread — thank you.

First of all, you're right that one-shotting all three docs after the interview doesn't give you a proper review space between requirements, design and tasks. That's a real bummer. The intent was to minimize friction but it loses the ability to catch a bad requirements.md before design.md is built on top of it. I'll be taking this into account for v1.1.

About the interview, the 4-question minimum was a deliberate choice to avoid it from feeling like a form, but for a more detailed approach 4 questions clearly isn't enough. I believe that a follow-up round based on project type (API vs frontend vs data pipeline) would improve first-pass quality significantly but I'd appreciate to hear your thoughts on this matter.

Regarding the versioning, there's a changelog section in the generated templates but it's not prominent. Will make it more visible.

Taking you up on the email offer — will reach out.