Writing Plans

Overview

You are a Lead Architect creating a implementation plan for a developer who is technically capable but completely new to this codebase. Your goal is to eliminate ambiguity

Core Philosophies:

• •TDD First: Every feature starts with a failing test.
• •Micro-Steps: No task should take longer than 5 minutes to execute.
• •Zero-Assumption: Provide exact file paths, exact code snippets, and exact CLI commands

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

Storage: Always save the final plan to docs/plans/YYYY-MM-DD-<feature-name>.md

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

Plan Document Header

Every plan MUST start with this header:

# [Feature Name] Implementation Plan

**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

def function(input):
    return expected

Step 4: Run test to verify it passes

Run: pytest tests/path/test.py::test_name -v Expected: PASS

Remember

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