---
name: Writing Plans
slug: writing-plans-6
category: Writing
description: Writing Plans helps you outline complex work before implementation. Use it for multi-step tasks, spec writing, architecture decisions, or when a change is too large to code in one pass.
github: "https://github.com/peintune/runjam/tree/main/src-tauri/builtin-skills/writing-plans"
language: Rust
stars: 195
forks: 12
install: "npx degit https://github.com/peintune/runjam/tree/main/src-tauri/builtin-skills/writing-plans ~/.claude/skills/writing-plans"
installs_to: ~/.claude/skills/writing-plans
source_path: src-tauri/builtin-skills/writing-plans/SKILL.md
collection_size: 13
category_size: 1279
collection_url: "https://dirskills.com/collections/peintune/runjam"
added: 2026-09-06T05:18:59.071Z
last_synced: 2026-09-06T05:18:59.071Z
canonical_url: "https://dirskills.com/skills/writing-plans-6"
---

# Writing Plans

Writing Plans helps you outline complex work before implementation. Use it for multi-step tasks, spec writing, architecture decisions, or when a change is too large to code in one pass.

**Install:**

```bash
npx degit https://github.com/peintune/runjam/tree/main/src-tauri/builtin-skills/writing-plans ~/.claude/skills/writing-plans
```

## README

# 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