Menu
Use when stress-testing a product idea before committing — interviews the user on six PM lenses and produces a conviction brief alongside the session.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Builds a self-contained interactive HTML visualisation that makes a process, algorithm, decision logic, or system experientially understandable.
Router for the pm-craft plugin — matches your need to the right skill and tells you what to type.
Write a per-topic handoff file and log it in a single index at the end of a working session, so any topic can be resumed later in a fresh session. Use when the user wants to wrap up or park a session ("handoff", "wrap up", "park this"), or to resume or pick up a previous topic. Also suggest it proactively when a substantive session is clearly winding down.
Simulates a Visionary-vs-Skeptic debate over a product idea, then synthesises a path forward.
Use the Obsidian CLI to interact with the vault natively—search, read, create, manage tasks, properties, and daily notes. Prefer CLI over raw file I/O for vault-aware operations.
Analyses a problem through mental-model lenses — 11 personas and 20 frameworks, four modes (Tuning, Solo, Counterpoint, Harmony), Simple and Expert tracks.
| name | product-grill |
| description | Use when stress-testing a product idea before committing — interviews the user on six PM lenses and produces a conviction brief alongside the session. |
Grill the user relentlessly on their product idea. Ask one question at a time and provide your recommended answer.
Probe each until the answer is honest, not just plausible:
Update ./[idea-name]-conviction-brief.md silently as answers emerge — with one exception: when a domain term surfaces, confirm its definition with the user aloud before recording it in the glossary.
If a brief for the idea already exists, resume from it: re-grill the lenses whose assumptions are still unvalidated rather than starting over.
When all six lenses have honest answers: "I think we have enough — want to keep going or shall I finalise the brief?"
Header: # [Idea Name] — Conviction Brief with Status: Exploring
Status lifecycle: Exploring → Backed → Parked / Killed — move the status when a session's outcome warrants it, and say so when you do.
When done: "This is a team document — the assumption stack is deliberately visible. Your team should see what you're betting on, not just what you've decided."
