Critique
Pushes back on logic gaps, missing assumptions, and weak arguments. Honest, not polite.
What it does
/critique reads a document and finds the weakest parts. Not style issues. Logic gaps, assumptions you haven't stated, arguments that don't hold up under pressure, and things you're avoiding saying.
The output is a list of specific problems with specific questions an adversarial reviewer would ask. If you can answer those questions, your document is ready. If you can't, the critique found the real issue.
When to use it
- Before sharing a PRD with engineering (they will find the gaps anyway)
- Before a leadership review where someone will push back hard
- When you want to stress-test your own reasoning before you commit to a direction
How to trigger it
Say: critique this doc and paste the document
Or: push back on this if you want a more conversational format
What you need
A document, spec, strategy memo, or structured argument. Works without integrations. The skill is sharper when you also tell it who the audience is and what their likely objections are. "Critique this PRD for an engineering lead who's skeptical of the scope" gives more useful output than a generic critique request.
Ready to install?
PM Pilot lives on GitHub. Every skill is a plain markdown file you can read, edit, and install in under 5 minutes.