How does this skill support Test-Driven Development (TDD)?

The skill mandates a TDD approach by requiring specific steps for writing a failing test, verifying the failure, and then implementing the minimal code to make it pass.

What is a Writing Plan in Claude Code?

A Writing Plan is a structured technical document created by this skill that breaks down a software feature into small, testable tasks including exact code examples and file paths.

How do I execute the plan once it is written?

After saving the plan, the skill offers two options: dispatching fresh subagents for each task within the current session or using parallel sessions for batch execution.

Where are the generated plans stored?

Plans are automatically saved as Markdown files in your repository under the docs/plans/ folder, organized by date and feature name.

Can I use this for projects I'm already working on?

Yes, it is specifically designed to handle existing codebases by providing explicit context, file paths, and line numbers to ensure no domain knowledge is assumed.

Implementation Planner

Name: Implementation Planner
Author: franroa

byfranroa

Productivity & Workflow

Generates hyper-detailed, step-by-step implementation plans using TDD principles and exact file paths for seamless feature development.

About

Implementation Planner is a specialized Claude Code skill designed to bridge the gap between high-level architectural design and technical execution. It transforms complex features into granular, bite-sized tasks—each taking only minutes to complete—while assuming zero prior codebase context for the implementer. By enforcing Test-Driven Development (TDD), DRY principles, and exact file path specifications, this skill ensures that developers or AI subagents can implement features with total precision, high reliability, and consistent version control hygiene.

Key Features

Automated plan documentation saved directly to the docs/plans/ directory
Granular task breakdown into 2-5 minute actionable steps
Explicit file path and line number mapping for all modifications
0 GitHub stars
TDD-first workflow requiring failing tests before any implementation
Integrated execution handoff for subagent-driven or parallel development

Use Cases

Breaking down complex features into manageable, test-verified commits
Providing clear instructions for engineers or AI agents with no codebase context
Ensuring rigorous TDD standards and documentation during fast-paced development

About

Key Features

Automated plan documentation saved directly to the docs/plans/ directory
Granular task breakdown into 2-5 minute actionable steps
Explicit file path and line number mapping for all modifications
0 GitHub stars
TDD-first workflow requiring failing tests before any implementation
Integrated execution handoff for subagent-driven or parallel development

Use Cases

Breaking down complex features into manageable, test-verified commits
Providing clear instructions for engineers or AI agents with no codebase context
Ensuring rigorous TDD standards and documentation during fast-paced development