What source documents does this skill require?

The skill looks for an analysis.md (typically created via an issue analysis) or a concept.md file within your workflow directory to use as the foundation for the plan.

How does it determine where to save the implementation plan?

It automatically detects your current git branch name (e.g., feature/42-something) and identifies the corresponding workflow folder, such as workflows/issue-42-*/, to store the plan.md.

How does this help with commit history?

The skill generates a commit strategy based on your project's COMMIT_GUIDELINES.md, outlining exactly how to sequence and describe your changes for a clean repository history.

Does the plan include testing requirements?

Yes, the skill reviews your project's TESTING_GUIDELINES.md to generate a specific test plan including unit and integration tests with defined purposes and file locations.

Can I customize the generated plan?

Absolutely. The skill produces a markdown-based plan.md that serves as a living document which you can further refine or adjust as the implementation progresses.

Implementation Plan Generator

Name: Implementation Plan Generator
Author: gittower

bygittower

•

184

Productivity & Workflow

Generates structured, task-based implementation plans from issue analysis or feature concepts within the Git-Flow Next ecosystem.

About

This skill automates the transition from requirements to execution by creating a comprehensive plan.md file tailored to your project's structure. By analyzing current git branch context and existing analysis documents, it breaks down complex features into actionable tasks while enforcing project-specific coding, testing, and commit guidelines. It is an essential tool for maintaining architectural consistency and ensuring that every implementation includes a robust test plan and a clear verification strategy before code is written.

Key Features

184 GitHub stars
Integration of project-specific coding, testing, and commit standards
Checkpoint-based verification strategy to ensure incremental build stability
Automated task breakdown with file paths, specific changes, and dependencies
Context-aware workflow folder detection based on active git branch naming
Structured test planning for both unit and integration testing scenarios

Use Cases

Translating an initial issue analysis into a concrete, executable development roadmap
Ensuring test-driven development practices are integrated into the planning phase of new features
Standardizing implementation strategies across teams using the Git-Flow Next workflow

About

Key Features

184 GitHub stars
Integration of project-specific coding, testing, and commit standards
Checkpoint-based verification strategy to ensure incremental build stability
Automated task breakdown with file paths, specific changes, and dependencies
Context-aware workflow folder detection based on active git branch naming
Structured test planning for both unit and integration testing scenarios

Use Cases

Translating an initial issue analysis into a concrete, executable development roadmap
Ensuring test-driven development practices are integrated into the planning phase of new features
Standardizing implementation strategies across teams using the Git-Flow Next workflow