Can I use this for existing codebases?

Yes. The skill is specifically designed to handle existing codebases by identifying exact file paths and line numbers to modify during the planning phase.

Where are the generated plans stored?

All implementation plans are automatically saved to the 'docs/plans/' directory of your repository using a standardized date-based naming convention.

How does the Writing Plans skill improve code quality?

It enforces Test-Driven Development (TDD) and the YAGNI principle by requiring a failing test for every small feature increment, ensuring all code is necessary and verified.

What is the difference between a plan and a subagent task?

A plan is a static roadmap of the entire feature; once saved, it can be executed task-by-task by subagents or via a separate parallel execution session.

Technical Implementation Planner

Name: Technical Implementation Planner
Author: zerdos

byzerdos

0•

Productivity & Workflow

Generates granular, TDD-focused implementation blueprints that break down complex requirements into bite-sized, executable tasks.

The Writing Plans skill transforms high-level specs and requirements into rigorous, step-by-step implementation guides. Designed for engineers who value precision, it enforces a Test-Driven Development (TDD) workflow by requiring failing tests and minimal code implementations for every 2-5 minute task. Each plan includes exact file paths, specific code snippets, and terminal commands, ensuring that even a developer with zero context can execute the feature perfectly. By documenting the architecture and tech stack upfront, it reduces technical debt and ensures consistency across the codebase.

Key Features

01Standardized markdown plan generation with YAML headers

02Automated TDD-driven task decomposition

03Seamless handoff to subagent or parallel execution workflows

040 GitHub stars

05Precise file path and line number mapping

06Pre-written failing tests and minimal implementations

Use Cases

01Mapping out complex features in unfamiliar or legacy codebases

02Enforcing strict testing and commit standards across a development team

03Creating reproducible implementation roadmaps for multi-step refactoring

Key Features

01Standardized markdown plan generation with YAML headers

02Automated TDD-driven task decomposition

03Seamless handoff to subagent or parallel execution workflows

040 GitHub stars

05Precise file path and line number mapping

06Pre-written failing tests and minimal implementations

Use Cases

01Mapping out complex features in unfamiliar or legacy codebases

02Enforcing strict testing and commit standards across a development team

03Creating reproducible implementation roadmaps for multi-step refactoring