How does it support Test-Driven Development (TDD)?

The skill explicitly structures tasks into cycles: write a failing test, run it to verify failure, implement minimal code, and verify the pass, enforcing rigorous testing habits.

Where are the generated plans stored?

Plans are automatically saved to the 'docs/plans/' directory using a standardized YYYY-MM-DD-feature-name.md format for easy version control and reference.

Can these plans be used by other developers?

Yes, the plans are written assuming the implementer is skilled but unfamiliar with the specific codebase, making them perfect for handovers and delegation.

What is the writing-plans skill?

It is a specialized capability for Claude Code that generates highly detailed, step-by-step implementation guides for new features or bug fixes, ensuring no detail is overlooked.

Implementation Plan Architect

Name: Implementation Plan Architect
Author: timbuchinger

bytimbuchinger

Productivity & Workflow

Generates detailed, step-by-step implementation plans with complete code examples and verification steps to streamline the transition from design to development.

About

The writing-plans skill transforms high-level designs into actionable, bite-sized tasks tailored for immediate execution or delegation within Claude Code. It emphasizes Test-Driven Development (TDD) and the DRY/YAGNI principles, ensuring that every task includes exact file paths, copy-pasteable code examples, and specific terminal commands for verification. By assuming minimal codebase familiarity, it creates a robust roadmap that minimizes ambiguity and technical debt, making it ideal for developer handovers or managing complex feature rollouts.

Key Features

Detailed verification steps with expected command outputs
Atomic task breakdown into 2-5 minute actionable steps
Automated plan storage in standardized documentation directories
Provision of complete, copy-pasteable code for implementation and tests
TDD-focused workflow including failing and passing test cycles
0 GitHub stars

Use Cases

Preparing structured work for team delegation or future execution sprints
Breaking down a finished design into concrete, executable development tasks
Ensuring consistent implementation standards across a distributed engineering team

About

Key Features

Detailed verification steps with expected command outputs
Atomic task breakdown into 2-5 minute actionable steps
Automated plan storage in standardized documentation directories
Provision of complete, copy-pasteable code for implementation and tests
TDD-focused workflow including failing and passing test cycles
0 GitHub stars

Use Cases

Preparing structured work for team delegation or future execution sprints
Breaking down a finished design into concrete, executable development tasks
Ensuring consistent implementation standards across a distributed engineering team