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/lidge-jun-writing-plans)
---
name: writing-plans
description: Use when you have a spec or requirements for a multi-step task, before touching code
---
# Writing Plans
## Goal
Write bite-sized, zero-context implementation plans. Assume the reader is a skilled developer with no knowledge of this codebase or problem domain.
- Run in a dedicated worktree (created by brainstorming skill)
- Save to `docs/plans/YYYY-MM-DD-<feature-name>.md`
- Principles: DRY, YAGNI, TDD, frequent commits
## Bite-Sized Task Granularity
**Each step is one action (2-5 minutes):**
- "Write the failing test" - step
- "Run it to make sure it fails" - step
- "Implement the minimal code to make the test pass" - step
- "Run the tests and make sure they pass" - step
- "Commit" - step
## Plan Document Header
```markdown
# [Feature Name] Implementation Plan
> **For Claude:** Use superpowers:executing-plans to implement this plan task-by-task.
**Goal:** [One sentence describing what this builds]
**Architecture:** [2-3 sentences about approach]
**Tech Stack:** [Key technologies/libraries]
---
```
## Task Structure
````markdown
### Task N: [Component Name]
**Files:**
- Create: `exact/path/to/file.py`
- Modify: `exact/path/to/existing.py:123-145`
- Test: `tests/exact/path/to/test.py`
**Step 1: Write the failing test**
```python
def test_specific_behavior():
result = function(input)
assert result == expected
```
**Step 2: Run test to verify it fails**
Run: `pytest tests/path/test.py::test_name -v`
Expected: FAIL with "function not defined"
**Step 3: Write minimal implementation**
```python
def function(input):
return expected
```
**Step 4: Run test to verify it passes**
Run: `pytest tests/path/test.py::test_name -v`
Expected: PASS
**Step 5: Commit**
```bash
git add tests/path/test.py src/path/file.py
git commit -m "feat: add specific feature"
```
````
## Checklist
- Exact file paths in every step
- Complete code (not "add validation")
- Exact commands with expected output
- Reference relevant skills with @ syntax
## Execution Handoff
After saving the plan, offer execution choice:
**"Plan saved to `docs/plans/<filename>.md`. Two execution options:**
**1. Subagent-Driven (this session)** — fresh subagent per task, review between tasks. Uses superpowers:subagent-driven-development.
**2. Parallel Session (separate)** — new session in worktree with superpowers:executing-plans, batch execution with checkpoints.
**Which approach?"**
