writing-plans

Generates detailed multi-step implementation plans with TDD tasks from specs.

1|Updated Jul 6, 2015
One-click install
npx skills add https://github.com/ksolomon/dotfiles --skill writing-plans-ksolomon
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/ksolomon/dotfiles/tree/main/AI/.claude/plugins/cache/claude-plugins-official/superpowers/6.1.1/skills/writing-plans
Command: npx skills add https://github.com/ksolomon/dotfiles --skill writing-plans-ksolomon

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a spec or requirements document into an actionable implementation plan is error-prone: tasks end up too vague, file paths are missing, and engineers without codebase context get stuck. This Skill produces a complete, bite-sized task plan that an engineer (or subagent) with zero context can execute directly. ## Core Features & Use Cases - Structured Plan Documents: Generates plans with a mandatory header (goal, architecture, tech stack, global constraints) and per-task blocks listing exact files to create or modify, interfaces consumed and produced, and checkbox steps. - Bite-Sized TDD Tasks: Breaks work into 2-5 minute steps following a failing-test, implement, verify, commit cycle, with complete code and exact commands in every step. - Self-Review and Handoff: Runs a spec-coverage, placeholder, and type-consistency check, then offers subagent-driven or inline execution of the finished plan. - Use Case: Given a feature spec for a new API endpoint, produce a dated plan file in docs/superpowers/plans/ with tasks covering tests, implementation, and commits that a fresh subagent can execute task-by-task. ## Quick Start Ask the AI to use the writing-plans skill to create an implementation plan from your spec before writing any code.

Frequently Asked Questions about writing-plans

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write an implementation plan from a spec before coding?▼

Provide the spec or requirements and invoke the writing-plans skill before touching code. It maps the file structure, decomposes work into right-sized tasks, and saves a dated plan document under docs/superpowers/plans/ with checkbox steps.

What makes a good task breakdown for AI coding agents?▼

Each task should be the smallest unit with its own test cycle and an independently testable deliverable. Steps should be 2-5 minute actions with exact file paths, complete code blocks, exact commands with expected output, and a commit step.

How does the plan handle test-driven development?▼

Every task follows a TDD cycle: write the failing test, run it to confirm failure, write the minimal implementation, run tests to confirm they pass, then commit. The plan includes the actual test code, not placeholders.

Can the plan be executed by subagents after it is written?▼

Yes. After saving the plan, the skill offers two execution options: subagent-driven development, which dispatches a fresh subagent per task with review between tasks, or inline execution with batch checkpoints.

What are common failure modes in AI-generated implementation plans?▼

Plan failures include placeholders like TBD or 'add error handling', steps without actual code, references to undefined types or functions, and inconsistent naming across tasks. The skill's self-review pass scans for these issues and fixes them inline.