writing-plans

Generates detailed multi-task implementation plans from specs using TDD and bite-sized steps.

1|Updated Oct 11, 2025
One-click install
npx skills add https://github.com/ibytechaos/claude --skill writing-plans-ibytechaos
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/ibytechaos/claude/tree/main/plugins/superpowers/skills/writing-plans
Command: npx skills add https://github.com/ibytechaos/claude --skill writing-plans-ibytechaos

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a spec or requirements document into an actionable implementation plan is error-prone: engineers get vague tasks, missing file paths, and placeholder steps that stall progress. This Skill produces complete, self-contained implementation plans that an engineer with zero codebase context can execute task by task. ## Core Features & Use Cases - Bite-Sized Task Decomposition: Breaks work into 2-5 minute steps following a strict TDD cycle (failing test, verify failure, minimal implementation, verify pass, commit). - No-Placeholder Enforcement: Requires exact file paths, complete code blocks, exact commands with expected output, and bans vague instructions like "add error handling" or "TBD". - Self-Review & Execution Handoff: Runs a spec-coverage, placeholder, and type-consistency check, then offers subagent-driven or inline execution of the finished plan. - Use Case: After brainstorming a new feature spec, invoke this Skill to produce a dated plan document in docs/superpowers/plans/ with checkbox-tracked tasks ready for subagent-driven implementation. ## Quick Start Ask the AI to use the writing-plans skill to turn your feature spec into a step-by-step TDD implementation plan saved under docs/superpowers/plans/.

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?

Provide the spec and invoke the writing-plans skill before touching code. It maps the file structure, decomposes work into bite-sized TDD tasks with exact paths and complete code, and saves the plan to docs/superpowers/plans/ as a dated Markdown file.

What makes a good task breakdown for AI-assisted coding?

Each step should be one 2-5 minute action: write the failing test, run it to confirm failure, implement minimal code, verify it passes, then commit. Every step needs exact file paths, full code blocks, and commands with expected output.

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 tasks self-contained and independently executable.

How are implementation plans executed after they are written?

The skill offers two options: subagent-driven development, which dispatches a fresh subagent per task with review between tasks, or inline execution using the executing-plans skill with batch execution and checkpoints.

What are common mistakes in AI-generated implementation plans?

Common failures include placeholders like TBD or "add error handling", missing code in steps, inconsistent function names across tasks, and references to undefined types. The skill's self-review pass scans for these issues before handoff.