Where are the implementation plans stored?

Plans are automatically saved as Markdown files in the docs/plans/ directory, using a YYYY-MM-DD-feature-name naming convention for easy version control.

How does it handle complex tasks?

The skill breaks down complex features into 'bite-sized' tasks that take only 2-5 minutes each, including the specific commands to run and the expected output.

Can I use this skill for team collaboration?

Yes, it is ideal for teams as it writes plans assuming the engineer has zero context, making the resulting documentation a perfect handoff tool for other developers or AI subagents.

Does it support different tech stacks?

While it includes patterns for Python and Swift/SwiftUI via indie-stack, its methodology of defining exact file paths and shell commands makes it adaptable to any programming environment.

What is the primary benefit of the Implementation Planner skill?

It prevents technical debt and scope creep by forcing a structured, test-first planning phase before any code is modified, ensuring every change is verified and documented.

Implementation Planner

Name: Implementation Planner
Author: bgrober

bybgrober

•

Productividad y Flujo de Trabajo

Generates granular, test-driven implementation plans that break down complex specs into executable, bite-sized tasks.

Acerca de

Implementation Planner is a high-precision workflow tool designed to bridge the gap between requirements and code. By enforcing a strict Test-Driven Development (TDD) approach, it creates a comprehensive roadmap of 2-5 minute tasks, each specifying exact file paths, failing test cases, minimal implementations, and commit commands. It is specifically built for developers who want to maintain high code quality through DRY and YAGNI principles while ensuring that even subagents or developers with zero project context can execute the feature flawlessly. The skill concludes by offering a seamless handoff to subagent-driven or parallel execution workflows.

Características Principales

Mandatory Test-Driven Development (TDD) cycle integration
Detailed file path and shell command documentation
1 GitHub stars
Standardized implementation headers for architectural clarity
Dual-mode handoff for subagent or parallel session execution
Bite-sized task granularity (2-5 minute actions)

Casos de Uso

Onboarding AI subagents with a foolproof, step-by-step technical roadmap
Maintaining strict test coverage and commit history during rapid prototyping
Architecting complex new features before writing a single line of production code

Acerca de

Características Principales

Mandatory Test-Driven Development (TDD) cycle integration
Detailed file path and shell command documentation
1 GitHub stars
Standardized implementation headers for architectural clarity
Dual-mode handoff for subagent or parallel session execution
Bite-sized task granularity (2-5 minute actions)

Casos de Uso

Onboarding AI subagents with a foolproof, step-by-step technical roadmap
Maintaining strict test coverage and commit history during rapid prototyping
Architecting complex new features before writing a single line of production code