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