The write-a-prd skill changed to to-prd, but doesn't interview

[JGormanAlphaSimplex]

Hello - I'm referencing commit 8868f54

The write-a-prd skill changed to to-prd, but it doesn't interview any longer.

What if I wanted an interview? What should I do know?

BTW: Burke Holland's excellent YouTube video piqued my interest: https://www.youtube.com/shorts/tA1C8kbno1c

Thanks.

[starkmarkus]

I think the interview behavior should still be available for exploratory PRD work. If to-prd no longer interviews by default, that feels more like a regression or a docs gap than an intentional simplification, because the conversational part is often the most useful entry point.

I’d either restore the interview-first flow or document the new explicit switch very clearly.

[Sampath7890]

This is intentional, not a regression. The split happened deliberately:

/to-prd now explicitly says "Do NOT interview the user — just synthesize what you already know." It's designed to be the last step of a workflow, not the first. GitHub
/grill-me is the interview step — it gets you "relentlessly interviewed about a plan or design until every branch of the decision tree is resolved." GitHub

So the intended flow is now: /grill-me → /to-prd → /to-issues — interview first, then synthesize into a PRD, then break into issues. They're meant to chain in the same conversation.
The old write-a-prd used to do both — interview then write — in a single skill. That's been split into two separate, composable steps. If you want the interview-first experience, just run /grill-me first, then /to-prd in the same session. Explainx