Our review

This skill generates a structured Markdown implementation plan document with progress tracking for steps and subtasks.

Provides a clear, standardized template for feature plans.
Uses emojis to indicate each step's status and an overall progress percentage.
Organizes critical decisions and tasks in a modular, minimal, and codebase-friendly way.

When to use it

Use it when a feature has been clarified through conversation and you need to formalize implementation steps before coding.

When not to use it

Avoid it for very small changes that don't need a formal plan, or for projects requiring specialized project management tools.

Examples

Plan for authentication feature

Create a feature implementation plan for adding user authentication to our existing Node.js app, based on the JWT approach we discussed.

Plan for refactoring legacy module

Produce a markdown plan for refactoring the payment module into separate services, with clear steps and progress tracking as specified.

Plan Creation Stage

Based on our full exchange, produce a markdown plan document.

Requirements for the plan:

Include clear, minimal, concise steps.
Track the status of each step using these emojis:
- 🟩 Done
- 🟨 In Progress
- 🟥 To Do
Include dynamic tracking of overall progress percentage (at top).
Do NOT add extra scope or unnecessary complexity beyond explicitly clarified details.
Steps should be modular, elegant, minimal, and integrate seamlessly within the existing codebase.

Markdown Template:

Feature Implementation Plan

Overall Progress: 0%

Short summary of what we're building and why.

Key architectural/implementation choices made during exploration:

...

Again, it's still not time to build yet. Just write the clear plan document. No extra complexity or extra scope beyond what we discussed.