I think we should close this, and once a given prompt is observed missing, we should open an issue/PR and do it.

I think we should actually sit and brainstorm useful prompts rather than rely on someone reporting that a prompt is missing. This is the kind of discoverability feature that wouldn't be functionality-breaking enough to have someone report its absence, but contributes to the polished DX.

I meant we should report them ourselves, but open specific issues as opposed to a meta one.

Right - I see this as more of the reminder for sitting down and deciding on the prompts. Once we've decided, we're going to open the corresponding issues and close this one.

This issue has gone 30 days without any activity and meets the project's definition of "stale". This will be auto-closed if there is no new activity over the next 30 days. If the issue is still relevant and active, you can simply comment with a "bump" to keep it open, or add the label "not_stale". Thanks for keeping our repository healthy!