菜单
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).
用 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.
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.
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.
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-plan |
| description | 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). |
Use this skill as the front door to the Ask Me Plan suite. It does not run the interview itself; it decides how deep the interview should go and which specialized Ask skills to bring in, states the route in one or two sentences, then continues as that skill.
Ask at most one short round (1-3 questions) to size the request:
If the user's first message already answers these implicitly (for example, a one-line request for a small, well-understood page), do not re-ask — infer the route and confirm it in one short sentence instead of running the triage questions.
| Signal | Route to |
|---|---|
| Small task, few unknowns, user wants speed | ask-light |
| Normal service, page, app, or feature | ask-standard |
| Complex, ambiguous, or high-stakes project | ask-deep |
| UI, design, or image style matters | also use ask-visual |
| Learning, teaching, student, or curriculum product | also use ask-educator |
| Plan feels underspecified, or rework would be costly | also use ask-risk |
| Interview is complete and needs a handoff prompt | ask-prompt |
| Plan is approved and ready to implement | ask-build |
If the user declines triage or planning entirely (for example: "no questions, just build", "skip planning"), first check whether the request is concrete enough to route and guess safely.
ask-build (or implement directly if no build skill is available).State the chosen route and why in one or two sentences, then continue the conversation as that skill. Do not produce a separate planning brief here — the routed skill owns that output.