When should I use this skill instead of just coding?

Use it for tasks requiring three or more distinct steps, complex integrations, or when you need a clear record for a handoff or future session.

What is the Implementation Planning skill?

It is a specialized capability for Claude Code that generates detailed, document-first blueprints for multi-step software implementation tasks.

Does it support Test-Driven Development?

Yes, the skill enforces a TDD cycle by requiring documentation for failing tests, minimal implementations, and verification steps for every atomic task.

Can Claude execute the plans it creates?

Yes, once a plan is generated, Claude provides options for subagent-driven execution or parallel session processing using specialized execution sub-skills.

Where are the plans saved?

Plans are automatically formatted and saved to the docs/plans/ directory in your project for version control and easy reference.

Implementation Planning

Name: Implementation Planning
Author: tachyon-beep

bytachyon-beep

•

Productivity & Workflow

Generates structured, atomic implementation plans for complex multi-step coding tasks to ensure consistency and reliable handoffs.

About

The Implementation Planning skill transforms complex software requirements into detailed, step-by-step blueprints designed for seamless execution by either the current AI session or a human engineer. By enforcing Test-Driven Development (TDD) principles and atomic task granularity, it ensures every change is independently testable, documented, and committable. The skill provides precise file paths, complete code examples, and exact verification commands, eliminating ambiguity and reducing errors during the development lifecycle.

Key Features

Standardized plan storage in project-relative markdown files
10 GitHub stars
Multi-option handoff protocols for subagent or parallel session execution
Integrated Test-Driven Development (TDD) workflow documentation
Atomic task breakdown with explicit Definitions of Done for every step
Precise file path and line-level modification guidance for complex codebases

Use Cases

Establishing a rigorous TDD cycle for mission-critical software components
Planning complex feature integrations requiring changes across multiple directories and services
Creating durable documentation for feature handoff between developers or AI sessions

About

Key Features

Standardized plan storage in project-relative markdown files
10 GitHub stars
Multi-option handoff protocols for subagent or parallel session execution
Integrated Test-Driven Development (TDD) workflow documentation
Atomic task breakdown with explicit Definitions of Done for every step
Precise file path and line-level modification guidance for complex codebases

Use Cases

Establishing a rigorous TDD cycle for mission-critical software components
Planning complex feature integrations requiring changes across multiple directories and services
Creating durable documentation for feature handoff between developers or AI sessions