菜单
Turn a vague idea or feature request into a written, reviewable spec and implementation plan before any code is written. Use when the user says "I want to build X", "help me think through", "I have an idea", or hands over an underspecified request.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
Workflow for building scalable messaging systems on Microsoft Azure using queues, event-driven architecture, pub/sub systems, service buses, and cloud-native communication patterns.
Workflow for implementing observability systems on Microsoft Azure using logging, monitoring, tracing, telemetry, metrics, dashboards, and production-grade cloud diagnostics.
Workflow for creating procedural systems in Blender using Geometry Nodes, procedural materials, node-based modeling, and non-destructive generation techniques.
Workflow for creating precise hard surface models in Blender using clean topology, subdivision workflows, bevel systems, and production-ready modeling techniques.
Workflow for using Claude to generate Blender Python scripts, automate 3D workflows, and create procedural scenes, animations, and assets directly inside Blender.
End-to-end workflow for setting up Blender, rigging a character, and creating a simple animation with a clear output (rendered animation).
基于 SOC 职业分类
| name | idea-to-plan |
| description | Turn a vague idea or feature request into a written, reviewable spec and implementation plan before any code is written. Use when the user says "I want to build X", "help me think through", "I have an idea", or hands over an underspecified request. |
Convert an underspecified request into (1) a one-paragraph problem statement, (2) a scoped spec, and (3) a phased implementation plan — each shown to the user for sign-off before moving on. Never jump to code from a vague prompt.
Do not use this for well-specified tasks, bug fixes with a clear repro, or mechanical changes — those go straight to implementation.
Write one paragraph: who has what problem, why now, and what "solved" looks like. Show it. If you can't write it, you don't understand the request — that gap is your first question.
Batch 3–6 questions that would change the design if answered differently. Skip anything with a safe default — state the default instead and move on. Good targets:
## Problem
## Goals / Non-goals
## Constraints
## Approach (1–3 sentences)
## Open questions
Keep it under one screen. Show it, get explicit "yes" on Goals/Non-goals before planning.
Break into phases that each deliver something verifiable:
Phase 1: <smallest end-to-end slice that proves the approach> — verify by <X>
Phase 2: ...
Each phase: concrete deliverable, the files/areas touched, and how it's verified. Flag dependencies and the riskiest phase. Front-load risk.
Output the spec + plan as the final artifact. Recommend the first phase and stop — implementation is a separate step the user triggers.