Create Plan
Goal
Turn a user prompt into a single, actionable plan delivered in the final assistant message.
Minimal workflow
Throughout the entire workflow, operate in read-only mode. Do not write or update files.
Scan context quickly
- Read
README.md and any obvious docs (docs/, CONTRIBUTING.md, ARCHITECTURE.md).
- Skim relevant files (the ones most likely touched).
- Identify constraints (language, frameworks, CI/test commands, deployment shape).
Ask follow-ups only if blocking
- Ask at most 1–2 questions.
- Only ask if you cannot responsibly plan without the answer; prefer multiple-choice.
- If unsure but not blocked, make a reasonable assumption and proceed.
Create a plan using the template below
- Start with 1 short paragraph describing the intent and approach.
- Clearly call out what is in scope and what is not in scope in short.
- Then provide a small checklist of action items (default 6–10 items).
- Each checklist item should be a concrete action and, when helpful, mention files/commands.
- Make items atomic and ordered: discovery → changes → tests → rollout.
- Verb-first: “Add…”, “Refactor…”, “Verify…”, “Ship…”.
- Include at least one item for tests/validation and one for edge cases/risk when applicable.
- If there are unknowns, include a tiny Open questions section (max 3).
Do not preface the plan with meta explanations; output only the plan as per template
Plan template (follow exactly)
# Plan
<1–3 sentences: what we’re doing, why, and the high-level approach.>
## Scope
- In:
- Out:
## Action items
[ ] <Step 1>
[ ] <Step 2>
[ ] <Step 3>
[ ] <Step 4>
[ ] <Step 5>
[ ] <Step 6>
## Open questions
- <Question 1>
- <Question 2>
- <Question 3>
Checklist item guidance
Good checklist items:
- Point to likely files/modules: src/..., app/..., services/...
- Name concrete validation: “Run npm test”, “Add unit tests for X”
- Include safe rollout when relevant: feature flag, migration plan, rollback note
Avoid:
- Vague steps (“handle backend”, “do auth”)
- Too many micro-steps
- Writing code snippets (keep the plan implementation-agnostic)
1---
2name: create-plan
3description: Create a concise plan. Use when a user explicitly asks for a plan related to a coding task.
4official: true
5metadata:
6 source: https://skillmd.com/skills/netease-youdao/create-plan
7 short-description: Create a plan
8---
9
10# Create Plan
11
12## Goal
13
14Turn a user prompt into a **single, actionable plan** delivered in the final assistant message.
15
16## Minimal workflow
17
18Throughout the entire workflow, operate in read-only mode. Do not write or update files.
19
201. **Scan context quickly**
21 - Read `README.md` and any obvious docs (`docs/`, `CONTRIBUTING.md`, `ARCHITECTURE.md`).
22 - Skim relevant files (the ones most likely touched).
23 - Identify constraints (language, frameworks, CI/test commands, deployment shape).
24
252. **Ask follow-ups only if blocking**
26 - Ask **at most 1–2 questions**.
27 - Only ask if you cannot responsibly plan without the answer; prefer multiple-choice.
28 - If unsure but not blocked, make a reasonable assumption and proceed.
29
303. **Create a plan using the template below**
31 - Start with **1 short paragraph** describing the intent and approach.
32 - Clearly call out what is **in scope** and what is **not in scope** in short.
33 - Then provide a **small checklist** of action items (default 6–10 items).
34 - Each checklist item should be a concrete action and, when helpful, mention files/commands.
35 - **Make items atomic and ordered**: discovery → changes → tests → rollout.
36 - **Verb-first**: “Add…”, “Refactor…”, “Verify…”, “Ship…”.
37 - Include at least one item for **tests/validation** and one for **edge cases/risk** when applicable.
38 - If there are unknowns, include a tiny **Open questions** section (max 3).
39
404. **Do not preface the plan with meta explanations; output only the plan as per template**
41
42## Plan template (follow exactly)
43
44```markdown
45# Plan
46
47<1–3 sentences: what we’re doing, why, and the high-level approach.>
48
49## Scope
50- In:
51- Out:
52
53## Action items
54[ ] <Step 1>
55[ ] <Step 2>
56[ ] <Step 3>
57[ ] <Step 4>
58[ ] <Step 5>
59[ ] <Step 6>
60
61## Open questions
62- <Question 1>
63- <Question 2>
64- <Question 3>
65```
66
67## Checklist item guidance
68Good checklist items:
69- Point to likely files/modules: src/..., app/..., services/...
70- Name concrete validation: “Run npm test”, “Add unit tests for X”
71- Include safe rollout when relevant: feature flag, migration plan, rollback note
72
73Avoid:
74- Vague steps (“handle backend”, “do auth”)
75- Too many micro-steps
76- Writing code snippets (keep the plan implementation-agnostic)