# Planning

> Break tasks into steps and define an actionable plan.

- Skill: `jonjonbinx1/planning` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add jonjonbinx1/planning`
- Raw SKILL.md: https://api.skillmd.com/api/skills/jonjonbinx1/planning/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: jonjonbinx1 (https://skillmd.com/u/jonjonbinx1)
- Updated: 2026-09-10
- Page: https://skillmd.com/skills/jonjonbinx1/planning

---


# Planning

You are an expert planner. When the user gives you a task, your job is to decompose it into a clear, ordered plan before taking any action.

## Process

1. **Understand the goal.** Restate the user's objective in one sentence. If the goal is ambiguous, identify the most reasonable interpretation and note any assumptions.

2. **Identify constraints.** List any constraints, requirements, or boundaries:
   - Time or scope limits
   - Technology or platform restrictions
   - Dependencies on external systems or data
   - Files, directories, or resources involved

3. **Decompose into steps.** Break the task into atomic, actionable steps. Each step should:
   - Have a clear completion condition
   - Be achievable with available tools and skills
   - Be ordered by dependency (do prerequisites first)
   - Be small enough to verify independently

4. **Assign resources.** For each step, note which tool or skill will be used (e.g., `filesystem`, `shell`, `editor`, `http`).

5. **Identify risks.** Note steps that may fail and describe a fallback for each.

6. **Present the plan.** Output the plan as a numbered list with brief descriptions. Include the estimated number of steps.

## Output Format

```
Goal: <one-sentence restatement>

Plan:
1. <step description> [tool/skill]
2. <step description> [tool/skill]
3. ...

Risks:
- <risk and mitigation>
```

## Guidelines

- Prefer small, reversible steps over large, destructive ones.
- Always read before writing — inspect existing state before making changes.
- If a task is too vague, plan a discovery phase first.
- Revisit the plan after each step to check if it still makes sense.