Is this skill suitable for large-scale features?

Absolutely. It is specifically designed to decompose large, multi-step requirements into manageable, verifiable units of work that minimize integration errors.

Does this skill help with unit testing?

Yes, it mandates a specific 'Write failing test' and 'Verify failure' sequence for every task to ensure 100% test coverage for new implementations.

Where are the implementation plans saved?

Plans are automatically saved as Markdown files in the docs/plans/ directory with a YYYY-MM-DD-feature-name.md format for easy tracking and versioning.

How do I execute a plan once it is created?

The skill provides a handoff option to either use a subagent-driven development workflow in the current session or a parallel session using the executing-plans sub-skill.

Why use an implementation plan instead of coding immediately?

Planning prevents technical debt and logic errors by enforcing DRY and YAGNI principles and ensuring edge cases are covered via TDD before any production code is written.

Technical Implementation Planner

Name: Technical Implementation Planner
Author: pur3v4d3r

bypur3v4d3r

•

Productividad y Flujo de Trabajo

Generates granular, test-driven implementation plans that break complex features into bite-sized, actionable development tasks.

Acerca de

The writing-plans skill transforms high-level specs and requirements into rigorous, step-by-step implementation roadmaps. It enforces industry best practices like Test-Driven Development (TDD), DRY, and YAGNI by requiring developers (or AI agents) to document exact file paths, failing test cases, and minimal code solutions before any work begins. By breaking down complex logic into 2-5 minute tasks with clear git commit checkpoints, it ensures high-quality output and provides a seamless handoff for subagent-driven or parallel session execution.

Características Principales

Enforces Test-Driven Development (TDD) with explicit failing/passing test steps
Includes architectural context and tech stack summaries for zero-context engineers
1 GitHub stars
Generates 2-5 minute bite-sized tasks for high-velocity development
Standardizes plan documentation in Markdown with automated date-based filing
Provides exact CLI commands and expected outputs for testing and commits

Casos de Uso

Onboarding developers or AI agents to unfamiliar repositories with precise roadmaps
Standardizing TDD and commit workflows across a distributed engineering team
Scaffolding complex features from requirements while maintaining codebase standards

Acerca de

Características Principales

Enforces Test-Driven Development (TDD) with explicit failing/passing test steps
Includes architectural context and tech stack summaries for zero-context engineers
1 GitHub stars
Generates 2-5 minute bite-sized tasks for high-velocity development
Standardizes plan documentation in Markdown with automated date-based filing
Provides exact CLI commands and expected outputs for testing and commits

Casos de Uso

Onboarding developers or AI agents to unfamiliar repositories with precise roadmaps
Standardizing TDD and commit workflows across a distributed engineering team
Scaffolding complex features from requirements while maintaining codebase standards