What is writing-plans?

The 'writing-plans' skill bridges the gap between high-level design and technical execution by generating comprehensive, step-by-step implementation plans. It optimizes the software development lifecycle (SDLC) by providing engineers—even those with zero codebase context—with exact file paths, functional code examples, and Test-Driven Development (TDD) verification steps, ensuring consistent and high-quality code output while minimizing domain-specific learning curves.

When should I use writing-plans?

writing-plans is useful in the following scenarios: • Feature Implementation Planning: Breaking down complex architectural designs into granular, actionable tasks with specific file modifications and code snippets to ensure DRY and YAGNI principles. • Developer Onboarding & Context Handoff: Streamlining the handoff process for new engineers or external contractors by providing a self-contained roadmap that requires minimal prior knowledge of the toolset. • TDD & Quality Assurance Standardization: Automating the creation of failing tests and minimal implementation steps to enforce rigorous testing standards and prevent regressions. • Agentic Workflow Orchestration: Generating structured task lists and plan documents optimized for autonomous execution by AI sub-agents or parallel development sessions.

name	writing-plans
description	Use when design is complete and you need detailed implementation tasks for engineers with zero codebase context - creates comprehensive implementation plans with exact file paths, complete code examples, and verification steps assuming engineer has minimal domain knowledge

Writing Plans

Overview

Write comprehensive implementation plans assuming the engineer has zero context for our 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 our toolset or problem domain. Assume they don't know good test design very well.

Announce at start: "I'm using the writing-plans skill to create the implementation plan." Save plans to: [Save to the same location as the design plan. Display location to user]

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

## CRITICAL: Present Tasks To User 1. Present the list of tasks to user, along with a 1 sentence description of the task 2. Use the `AskUserTool` to your partner if they approve the tasks 3. I will be disappointed if you start writing an implement plan before presenting me a list of tasks

Plan Document Header

Every plan MUST start with this header:

# [Feature Name] Implementation Plan

> **For Claude:** REQUIRED SUB-SKILL: 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

## Task {{task-number}} - {{task-name}}

### Files
- `exact/path/to/file.py` (CREATE)
- `exact/path/to/existing.py:123-145` (MODIFY)
- `tests/exact/path/to/test.py` (CREATE & TEST)

### 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
Use `create-git-commit` skill to commit

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, frequent commits

Execution Handoff

After saving the plan, offer execution choice:

"Plan complete and saved to {{implement-plan-path}}. Two execution options:

1. Subagent-Driven (this session) - I dispatch fresh subagent per task, review between tasks, fast iteration

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

Which approach?"

If Subagent-Driven chosen:

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

If Parallel Session chosen:

Guide them to open new session in worktree
REQUIRED SUB-SKILL: New session uses superpowers:executing-plans

writing-plans

When & Why to Use This Skill

Use Cases