writing-plans

Generates detailed implementation plans with bite-sized TDD tasks from feature specifications.

Updated Jul 23, 2025
One-click install
npx skills add https://github.com/derrik-fleming/dotfiles --skill writing-plans-derrik-fleming
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/derrik-fleming/dotfiles/tree/main/private_dot_agents/skills/writing-plans
Command: npx skills add https://github.com/derrik-fleming/dotfiles --skill writing-plans-derrik-fleming

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Engineers often start coding from a spec without a concrete roadmap, leading to missed requirements, vague tasks, and inconsistent execution. This Skill turns a spec or requirements document into a complete, step-by-step implementation plan that any engineer can follow without prior codebase context. ## Core Features & Use Cases - Bite-Sized Task Decomposition: Breaks work into 2-5 minute steps following TDD: write failing test, verify failure, implement, verify pass, commit. - No-Placeholder Enforcement: Requires exact file paths, complete code blocks, and exact commands with expected output in every step. - Self-Review Checklist: Validates spec coverage, scans for placeholder patterns, and checks type consistency across tasks before handoff. - Execution Handoff: Offers subagent-driven or inline execution paths after saving the plan to docs/superpowers/plans/. - Use Case: Given a spec for a new API endpoint, produce a dated plan document where each task lists exact files to create or modify, full test code, implementation code, and commit commands. ## Quick Start Ask the AI to use the writing-plans skill to create an implementation plan from your feature 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 feature spec?▼

Map out the file structure first, then decompose work into tasks where each step is one 2-5 minute action: write a failing test, run it, implement minimal code, verify it passes, and commit. Every step needs exact file paths and complete code, never placeholders.

What is a good task granularity for implementation plans?▼

Each step should be a single action taking 2-5 minutes, such as writing one failing test or running one command. Tasks group related steps around one component and should produce self-contained, independently testable changes.

When should a spec be split into multiple implementation plans?▼

Split when the spec covers multiple independent subsystems. Each plan should produce working, testable software on its own, so one plan per subsystem keeps scope manageable and execution verifiable.

Why do implementation plans fail during execution?▼

Plans fail when they contain placeholders like TODO or vague steps such as add error handling, reference undefined types or functions, or use inconsistent names across tasks. A self-review for spec coverage, placeholders, and type consistency catches these issues.

Can I execute a plan with subagents instead of inline?▼

Yes, after saving the plan you can choose subagent-driven execution, which dispatches a fresh subagent per task with review between tasks, or inline execution, which runs tasks in batches with checkpoints in the current session.