Codify a Product Review Checklist as a Cursor Skill

When I use Cursor, I often turn “product proposal review” into a Skill—not so AI can decide for me, but so every review covers the same critical questions.

What this Skill solves

• Easy to skip “success metrics” and “failure signals”
• Uneven question quality across teammates
• New joiners lack a reusable questioning frame

How I use it

1. Paste the proposal context (user, problem, solution, scope)
2. Trigger the Skill to probe gaps against the checklist
3. Keep only questions that change the decision, and bring them to the review

Caveats

A Skill is not the decision-maker. It improves question coverage; priority, resources, and politics still need humans. Treat it as a quality gauge, not a substitute PM.

If you want your own checklist, start with three questions: who is the user, what does success look like, and where are we most likely wrong.