Use when you have a spec or requirements for a multi-step task, before touching code. Creates bite-sized TDD implementation plans with dependency tracking.
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/a5c-ai-writing-plans)
---
name: writing-plans
description: Use when you have a spec or requirements for a multi-step task, before touching code. Creates bite-sized TDD implementation plans with dependency tracking.
---
# Writing Plans
## Overview
Create comprehensive implementation plans with bite-sized tasks (2-5 minutes each). Every task has exact file paths, complete code, verification steps, and TDD flow.
**Core principle:** Document everything the engineer needs. DRY. YAGNI. TDD. Frequent commits.
## When to Use
- After design approval (from brainstorming)
- When you have specs/requirements for multi-step work
- Before any implementation begins
## Task Structure
Each task follows: Write failing test -> Verify fail -> Implement minimal code -> Verify pass -> Commit
## Plan Format
- Header: Goal, Architecture, Tech Stack
- Tasks with exact file paths and complete code
- TDD steps with expected output
- Task persistence via `.tasks.json`
## Execution Handoff
After plan is written, choose:
1. **Subagent-Driven** - Fresh agent per task with two-stage review
2. **Batch Execution** - Execute in batches with human checkpoints
## Agents Used
- Process agents defined in `writing-plans.js`
## Tool Use
Invoke via babysitter process: `methodologies/superpowers/writing-plans`
