菜单
Use when stress-testing a product idea before committing — interviews the user on six PM lenses and produces a conviction brief alongside the session.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| 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. Build the conviction brief silently as answers emerge.
Probe each until the answer is honest, not just plausible:
Update ./[idea-name]-conviction-brief.md silently as answers emerge. Extract domain terms to the glossary as they come up — confirm definitions before writing the file.
When all six lenses have honest answers: "I think we have enough — want to keep going or shall I write it up?"
Header: # [Idea Name] — Conviction Brief with Status: Exploring
Status lifecycle: Exploring → Backed → Parked / Killed
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."
Builds a self-contained interactive HTML visualisation that makes a process, algorithm, decision logic, or system visually and experientially understandable. Primary input is a linear walkthrough, but works directly from code, documents, or concept descriptions too — and can invoke the linear-walkthrough skill as an intermediate step if the source material lacks sufficient clarity or structure. Use when the user wants to "see how this works", wants an interactive version of a walkthrough, wants to explain a process visually to an audience, or asks to "visualise", "animate", or "build an interactive explanation" of anything. Richer and more interactive is always preferred, as long as it makes the logic clearer rather than decorating it.
Generates a linear, narrative walkthrough of source material — code, documents, architecture diagrams, meeting notes, Jira tickets, or any combination. Produces a step-by-step guide that explains logic, purpose, and connections between components in a readable sequence. Use when the user wants to understand how something works, wants to explain a system to others, asks to "walk through" or "explain" code or docs, or needs to document a system's logic for learning or onboarding. Also trigger when the user provides files or code and asks "how does this work?" or "take me through this."
Converts Markdown files to Google Docs-friendly DOCX format using Pandoc (via a helper script).
Use the Obsidian CLI to interact with the vault natively—search, read, create, manage tasks, properties, daily notes, and more. Prefer CLI over raw file I/O for vault-aware operations.
