Where does Claude save the generated implementation plans?

Plans are automatically saved to the 'docs/plans/' directory using a standardized YYYY-MM-DD-feature-name.md naming convention.

Can I use these plans for automated execution?

Yes, once a plan is saved, you can use the 'executing-plans' skill to work through the tasks either manually or via subagent execution.

What is the primary purpose of the Writing Plans skill?

It is designed to decompose complex features into tiny, 2-5 minute tasks that include testing and verification steps to ensure high-quality code implementation.

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

The skill structures every task to start with a failing test, followed by a verification command, the implementation code, and finally a passing test confirmation.

Writing Plans

Name: Writing Plans
Author: a-ariff

bya-ariff

Productivity & Workflow

Generates granular, step-by-step implementation plans using TDD principles to streamline complex development workflows.

About

Writing Plans is a specialized Claude Code skill designed to bridge the gap between architectural design and code execution by breaking down complex features into bite-sized, executable tasks. By enforcing a strict TDD workflow—including failing tests, implementation steps, and atomic commits—this skill creates a comprehensive roadmap that ensures codebase stability and allows for easy handoff. It automatically generates standardized documentation in your repository, ensuring that every code change is purposeful, verified, and manageable even for developers with zero initial context.

Key Features

Atomic git commit strategy mapping
Standardized Markdown plan generation
0 GitHub stars
Micro-task decomposition (2-5 minute steps)
Integrated Test-Driven Development (TDD) cycles
Explicit file path and code snippet definitions

Use Cases

Breaking down complex refactors into manageable, low-risk steps
Creating documentation-first roadmaps for team collaboration
Transitioning from high-level design to technical execution

About

Key Features

Atomic git commit strategy mapping
Standardized Markdown plan generation
0 GitHub stars
Micro-task decomposition (2-5 minute steps)
Integrated Test-Driven Development (TDD) cycles
Explicit file path and code snippet definitions

Use Cases

Breaking down complex refactors into manageable, low-risk steps
Creating documentation-first roadmaps for team collaboration
Transitioning from high-level design to technical execution