メニュー
Planning risk interview for finding assumptions, contradictions, missing requirements, privacy issues, UX gaps, education-specific gaps, and implementation ambiguity before building. Use when a plan feels underspecified or when rework would be costly.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Convert an Ask planning interview, notes, product brief, or clarified idea into an implementation-ready prompt for Codex or another coding agent. Use after ask-light, ask-standard, ask-deep, ask-visual, ask-educator, or ask-risk when the user needs a precise handoff prompt.
Detailed, multi-round planning interview for complex services, apps, websites, education products, AI workflows, or ambiguous projects where premature implementation would create rework. Use when the user wants many questions, deep clarification, or a full planning pass before implementation.
Fast, low-friction planning interview for vague product, web page, app, education content, feature, or implementation requests. Use when the user wants a quick plan before building, wants only a few clarifying questions, or asks for a lightweight "ask before build" pass.
Entry point for the Ask Me Plan skill suite. Use when the user wants to plan something before building but has not said how deep the interview should be, or is not sure which Ask skill fits (quick, standard, deep, visual, education, risk, prompt, or build).
Balanced planning interview for service planning, web pages, apps, education content, product features, and implementation work. Use when the user wants the agent to ask clarifying questions before building and produce a practical implementation prompt.
Start implementation from an approved Ask planning prompt. Use after ask-prompt or a completed Ask planning interview when the user has a concrete plan and wants Codex to build, preferably with builder, reviewer, and QA subagents when multi-agent tools are available.
| name | ask-risk |
| description | Planning risk interview for finding assumptions, contradictions, missing requirements, privacy issues, UX gaps, education-specific gaps, and implementation ambiguity before building. Use when a plan feels underspecified or when rework would be costly. |
Use this skill to find what the AI might misunderstand before implementation starts. Focus on questions that prevent rework, not theoretical completeness.
Review the plan for:
Ask only high-impact questions. Prefer 3-7 targeted questions.
Use this pattern:
Return:
Before -> After (addresses: <risk>). Include only what actually changed, not the full plan.Move blocking questions into the running plan's Open Questions, non-blocking items into Assumptions, and apply the recommended changes directly to Confirmed Decisions before handing off to ask-prompt. Pass the change log along with the updated plan — it is how ask-prompt checks that nothing found during risk review got lost on the way to the final prompt.