What makes a writing-plan different from a standard task list?

Writing-plans are hyper-specific, including exact file paths, the actual code to be written, and the specific shell commands needed to verify each step using Test-Driven Development.

Can these plans be executed automatically by Claude?

Yes, the skill includes a handoff mechanism to either use a subagent-driven development approach within the current session or a parallel session using executing-plans.

Do I need to know the codebase to use these plans?

No, the skill is designed specifically for engineers with zero context, providing all the necessary domain knowledge and file locations within the plan itself.

Where are the generated plans stored?

Plans are automatically saved as Markdown files in the docs/plans/ directory using a standardized YYYY-MM-DD-feature-name.md naming convention.

Writing Plans

Name: Writing Plans
Author: Microck

byMicrock

•

Productivity & Workflow

Generates detailed, step-by-step implementation plans for engineers with zero codebase context using TDD principles.

About

This skill automates the creation of comprehensive technical roadmaps by breaking down complex features into bite-sized, executable tasks. It assumes minimal domain knowledge from the developer, providing exact file paths, complete code snippets, and specific verification commands for every step. By enforcing Test-Driven Development (TDD), DRY, and YAGNI principles, it ensures high-quality code output and seamless handoffs between Claude and human engineers or automated subagents.

Key Features

Automates TDD workflows including failing tests and minimal implementations
81 GitHub stars
Integrates with subagent and parallel session execution workflows
Standardizes plan documentation in a dedicated directory for better traceability
Generates bite-sized tasks designed for 2-5 minute completion windows
Provides exact file paths and line-specific modification instructions

Use Cases

Scaffolding new features while ensuring strict adherence to TDD and DRY principles
Onboarding developers to a complex codebase with a clear task-by-task roadmap
Preparing detailed technical handoff documentation for subagents or remote teams

About

Key Features

Automates TDD workflows including failing tests and minimal implementations
81 GitHub stars
Integrates with subagent and parallel session execution workflows
Standardizes plan documentation in a dedicated directory for better traceability
Generates bite-sized tasks designed for 2-5 minute completion windows
Provides exact file paths and line-specific modification instructions

Use Cases

Scaffolding new features while ensuring strict adherence to TDD and DRY principles
Onboarding developers to a complex codebase with a clear task-by-task roadmap
Preparing detailed technical handoff documentation for subagents or remote teams