# Writing Plans

> Use when you have a spec or requirements for a multi-step task, before touching code

- **Type:** Skill
- **Install:** `agentstack add skill-himmelreich-it-agent-skill-converter-writing-plans`
- **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior
- **Seller:** [himmelreich-it](https://agentstack.voostack.com/s/himmelreich-it)
- **Installs:** 0
- **Category:** [Agent Skills](https://agentstack.voostack.com/c/agent-skills)
- **Latest version:** 0.1.0
- **License:** Apache-2.0
- **Upstream author:** [himmelreich-it](https://github.com/himmelreich-it)
- **Source:** https://github.com/himmelreich-it/agent-skill-converter/tree/main/out/junie/skills/superpowers/skills/writing-plans

## Install

```sh
agentstack add skill-himmelreich-it-agent-skill-converter-writing-plans
```

Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent.

## About

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

**Context:** This should be run in a dedicated worktree if possible.

**Save plans to:** `docs/superpowers/plans/YYYY-MM-DD-.md`
- (User preferences for plan location override this default)

## Scope Check

If the spec covers multiple independent subsystems, suggest breaking this into separate plans — one per subsystem. Each plan should produce working, testable software on its own.

## File Structure

Before defining tasks, map out which files will be created or modified and what each one is responsible for.

- Design units with clear boundaries and well-defined interfaces. Each file should have one clear responsibility.
- Smaller, focused files are preferred over large ones.
- In existing codebases, follow established patterns.

## 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 (using Junie's co-authored trailer if applicable)

## Plan Document Header

**Every plan MUST start with this header:**

```markdown
# [Feature Name] Implementation Plan

> **For Junie:** REQUIRED: Use `superpowers:subagent-driven-development` or `superpowers:executing-plans` to implement this plan. Steps use checkbox (`- [ ]`) syntax for tracking.

**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`
- 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" --trailer "Co-authored-by: Junie "
```
````

## Remember
- Exact file paths always.
- Complete code in plan.
- Exact commands with expected output.
- Reference relevant skills using `agent_skill_read_doc` logic.
- DRY, YAGNI, TDD, frequent commits.

## Plan Review Loop

After completing each chunk of the plan, review it for consistency and quality. Use `update_status` to track the review progress.

## Execution Handoff

After saving the plan:

**"Plan complete and saved to `docs/superpowers/plans/.md`. Ready to execute?"**

**Execution path for Junie:**
- **REQUIRED:** Use `superpowers:subagent-driven-development`.
- Use `update_status` to maintain the persistent plan and status.
- Fresh sub-task/persona per task + review.

## Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

- **Author:** [himmelreich-it](https://github.com/himmelreich-it)
- **Source:** [himmelreich-it/agent-skill-converter](https://github.com/himmelreich-it/agent-skill-converter)
- **License:** Apache-2.0

Install and usage instructions live in the source repository linked above.

## Pricing

- **Free** — Free

## Security capabilities

Automated source analysis of v0.1.0 — what this tool can access:

- **Network access:** no
- **Filesystem access:** no
- **Shell / process execution:** no
- **Environment & secrets:** no
- **Dynamic code execution:** no

*"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.*


## Versions

- **0.1.0** — security scan: passed — Imported from the upstream source.

## Links

- Listing page: https://agentstack.voostack.com/l/skill-himmelreich-it-agent-skill-converter-writing-plans
- Seller: https://agentstack.voostack.com/s/himmelreich-it
- Browse the marketplace: https://agentstack.voostack.com/browse

---
Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.