Use for complex multi-step tasks. Create a structured plan before writing code. Use when the user asks for a plan, spec, or when the task is too large to implement in one step.
Installs into .claude/skills of the current project.
Are you the author of Writing Plans?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/peintune-writing-plans)
---
name: writing-plans
description: "Use for complex multi-step tasks. Create a structured plan before writing code. Use when the user asks for a plan, spec, or when the task is too large to implement in one step."
---
# Writing Plans
For complex tasks, always plan before implementing.
## Plan Structure
1. **Goal**: What are we trying to achieve?
2. **Approach**: High-level strategy
3. **Steps**: Ordered, actionable items
4. **Risks**: What could go wrong?
5. **Alternatives**: What else was considered?
## When to Plan
- Task spans multiple files or modules
- User explicitly asks for a plan
- Architecture decisions are needed
- Breaking changes to existing APIs
## Anti-Patterns
- Planning for trivial tasks (single-file, single-function)
- Over-planning: more time planning than coding
- Plan has no action items — just abstract theory
