Where are the implementation plans saved?

Plans are automatically saved as standardized markdown files in the docs/plans/ directory using a date-stamped filename for easy tracking.

Can I use this for existing projects with no documentation?

Yes, the skill is designed to analyze existing codebases and provide specific file paths and context for modifications, even for developers with zero prior knowledge.

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

It explicitly defines failing tests, expected failures, and minimal implementation steps for every individual task in the plan, ensuring quality from the start.

What happens after the planning phase is complete?

The skill offers a handoff choice between subagent-driven development for fast iteration or parallel session execution for batch task processing.

Implementation Plan Architect

Name: Implementation Plan Architect
Author: julianromli

byjulianromli

•

101

Productivity & Workflow

Generates comprehensive, TDD-driven implementation plans for complex software tasks before writing a single line of code.

About

The writing-plans skill empowers developers to architect detailed, multi-step implementation strategies for complex features. By assuming a 'zero-context' mindset, it produces bite-sized, test-driven development (TDD) tasks that include exact file paths, shell commands, and expected outputs. This skill ensures structural integrity, follows YAGNI and DRY principles, and facilitates a smooth handoff to execution sub-agents or parallel coding sessions, making it ideal for teams requiring high documentation standards and rigorous testing workflows.

Key Features

Automated plan documentation in standardized markdown format
101 GitHub stars
Flexible handoff options for sub-agent or parallel execution
Exact file path and line-specific modification mapping
TDD-first task generation with failing test examples
Integrated 'zero-context' engineering documentation for better codebase onboarding

Use Cases

Creating standardized implementation documentation for complex architectural changes
Enforcing TDD practices across a codebase for new contributors
Mapping out large feature requests into manageable, 5-minute tasks

About

Key Features

Automated plan documentation in standardized markdown format
101 GitHub stars
Flexible handoff options for sub-agent or parallel execution
Exact file path and line-specific modification mapping
TDD-first task generation with failing test examples
Integrated 'zero-context' engineering documentation for better codebase onboarding

Use Cases

Creating standardized implementation documentation for complex architectural changes
Enforcing TDD practices across a codebase for new contributors
Mapping out large feature requests into manageable, 5-minute tasks