sp-writing-plans

name	sp-writing-plans
description	Converts approved designs into comprehensive, bite-sized implementation plans. Use when you have a spec or requirements for a multi-step task, before touching code.
tags	["planning","workflow","implementation","tdd"]
version	1.0.0
risk	guarded
triggers	["write an implementation plan","create a plan for this","plan this feature","write a plan","make a plan","implementation plan","plan before coding"]
requirements	{"cli":[],"env":[]}
upstream_ref	skills/writing-plans/SKILL.md
author	AlphaComposite
license	MIT
dependencies	["sp-brainstorming","sp-subagent-driven-development","sp-executing-plans","sp-using-git-worktrees"]

Writing Plans

Overview

Write comprehensive implementation plans assuming the engineer has zero context for the codebase and questionable taste. Document everything they need to know: which files to touch for each task, code, testing, docs they might need to check, how to test it. Give them the whole plan as bite-sized tasks. DRY. YAGNI. TDD. Frequent commits.

Assume they are a skilled developer, but know almost nothing about the toolset or problem domain. Assume they don't know good test design very well.

Announce at start: "I'm using the sp-writing-plans skill to create the implementation plan."

Context: This should be run in a dedicated worktree (created by sp-brainstorming via sp-using-git-worktrees).

Save plans to: docs/plans/YYYY-MM-DD-<feature-name>.md

Dependency note: sp-subagent-driven-development and sp-executing-plans are referenced in the Execution Handoff section. If either is unavailable, inform the user and describe the manual equivalent.

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

Every plan MUST start with this header:

# [Feature Name] Implementation Plan

> **For the agent:** REQUIRED SUB-SKILL: Use `sp-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

### 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"
```

Remember

• Exact file paths always
• Complete code in plan (not "add validation")
• Exact commands with expected output
• Reference relevant skills by name
• DRY, YAGNI, TDD, frequent commits

Execution Handoff

After saving the plan, offer execution choice:

"Plan complete and saved to docs/plans/<filename>.md. Two execution options:

1. Subagent-Driven (this session) — Dispatch a fresh subagent per task, review between tasks, fast iteration

2. Parallel Session (separate) — Open new session with sp-executing-plans, batch execution with checkpoints

Which approach?"

If Subagent-Driven chosen:

• REQUIRED SUB-SKILL: Use sp-subagent-driven-development
• Stay in this session
• Fresh subagent per task + code review

If Parallel Session chosen:

• Guide them to open a new session in the worktree
• REQUIRED SUB-SKILL: New session uses sp-executing-plans