How does this skill improve code quality?

By enforcing a test-first approach and breaking tasks into 2-5 minute steps, it minimizes logic errors and ensures every change is verified by a passing test.

Where are the implementation plans saved?

Plans are automatically saved to the `docs/plans/` directory with a standardized naming convention (YYYY-MM-DD-feature-name.md) for easy tracking.

Can I execute the plans automatically after they are created?

Yes, once a plan is saved, the skill offers a handoff to either subagent-driven development or parallel session execution for automated implementation.

What coding principles does this skill follow?

The skill strictly adheres to DRY (Don't Repeat Yourself), YAGNI (You Ain't Gonna Need It), TDD (Test-Driven Development), and frequent commit patterns.

What is the primary focus of the Writing Plans skill?

The skill focuses on creating detailed, granular implementation plans that follow TDD and DRY principles, ensuring all code changes are planned before execution.

Writing Plans

Name: Writing Plans
Author: monkey1sai

bymonkey1sai

Productivity & Workflow

Generates detailed, step-by-step implementation plans for complex software tasks following TDD and clean code principles.

About

The Writing Plans skill transforms Claude into a technical architect, drafting comprehensive implementation roadmaps before a single line of production code is written. It specializes in breaking down high-level requirements into granular, 2-5 minute tasks that emphasize Test-Driven Development (TDD), DRY principles, and frequent commits. This skill is ideal for complex features where maintaining context, ensuring test coverage, and providing clear handoff instructions for subagents or team members is critical for project success.

Key Features

Seamless handoff to subagent-driven or parallel execution modes
Standardized plan archiving in version-controlled documentation directories
Granular task breakdown into 2-5 minute actionable steps
Precise file path and code snippet mapping for zero-context environments
0 GitHub stars
Embedded Test-Driven Development (TDD) workflows for every task

Use Cases

Mapping out a new feature implementation from a technical specification
Executing complex refactoring projects with strict TDD requirements
Creating clear, executable documentation for onboarding developers to a codebase

About

Key Features

Seamless handoff to subagent-driven or parallel execution modes
Standardized plan archiving in version-controlled documentation directories
Granular task breakdown into 2-5 minute actionable steps
Precise file path and code snippet mapping for zero-context environments
0 GitHub stars
Embedded Test-Driven Development (TDD) workflows for every task

Use Cases

Mapping out a new feature implementation from a technical specification
Executing complex refactoring projects with strict TDD requirements
Creating clear, executable documentation for onboarding developers to a codebase