메뉴
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.
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.
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).
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-standard |
| description | 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. |
Use this skill as the default "ask before build" workflow. Interview the user in their language, reduce ambiguity, and produce an implementation-ready prompt.
If the user explicitly declines the interview (for example: "no questions, just build", "skip planning"), first check whether the request is concrete enough to guess safely.
Ask 8-12 questions across 2-4 short rounds. Do not dump every question at once unless the user asks for a form. After each answer, update the working plan before asking the next question. The skill should feel like a guided conversation, not a static questionnaire.
Round 1: Define the job
Round 2: Shape the product
Round 3: Confirm execution details
Use related Ask skills when they fit:
ask-visual for UI, design, image style, brand, or reference-app decisions.ask-educator for education products, learning content, assessment, curriculum, student feedback, or teacher dashboards.ask-risk when the plan has hidden assumptions, contradictions, privacy risk, or unclear success criteria.ask-prompt after the interview to create the final implementation prompt.If the interview runs long or spans multiple sessions, write the plan to a PLAN.md file in the project root instead of relying on chat history alone, and keep it updated as answers come in.
Group the brief under the shared Ask Me Plan headers so ask-visual, ask-educator, ask-risk, and ask-prompt can build on it without re-asking:
End by naming which Ask skill fits best next (ask-visual, ask-educator, ask-risk, or ask-prompt), and ask whether the user wants to start implementation only if ask-build is in scope.