ce:plan
将 WHAT 转换为 HOW，生成可跟踪的实施步骤与里程碑。
把需求或目标拆解为结构化的可执行实施计划。
把模糊的需求或目标拆成清晰、按步可执行的实施计划，包含任务、依赖、里程碑和估时。适合要落地开发、研究、活动或学习计划时，把 brainstorm 或需求文档变成可交付方案用。特点是把 WHAT 转换为 HOW，产出可追踪的实施路线而不直接写代码。
▸ 展开 SKILL.md 英文原文
Create structured plans for any multi-step task -- software features, research workflows, events, study plans, or any goal that benefits from structured breakdown. Also deepen existing plans with interactive review of sub-agent findings. Use for plan creation when the user says 'plan this', 'create a plan', 'write a tech plan', 'plan the implementation', 'how should we build', 'what's the approach for', 'break this down', 'plan a trip', 'create a study plan', or when a brainstorm/requirements document is ready for planning. Use for plan deepening when the user says 'deepen the plan', 'deepen my plan', 'deepening pass', or uses 'deepen' in reference to a plan. For exploratory or ambiguous requests where the user is unsure what to do, prefer ce:brainstorm first.
帮我安装这个 skill：https://raw.githubusercontent.com/MaximoCorrea1/ultra-powers/main/flows/ultra-powers/skills/ce-plan/SKILL.mdcurl -fsSL "https://raw.githubusercontent.com/MaximoCorrea1/ultra-powers/main/flows/ultra-powers/skills/ce-plan/SKILL.md"# Create Technical Plan **Note: The current year is 2026.** Use this when dating plans and searching for recent documentation. `ce:brainstorm` defines **WHAT** to build. `ce:plan` defines **HOW** to build it. `ce:work` executes the plan. This workflow produces a durable implementation plan. It does **not** implement code, run tests, or learn from execution-time results. If the answer depends on changing code and seeing what happens, that belongs in `ce:work`, not here. ## Interaction Method Use the platform's question tool when available. When asking the user a question, prefer the platform's blocking question tool if one exists (`AskUserQuestion` in Claude Code, `request_user_input` in