Our review

Generates a structured markdown feature implementation plan with progress tracking, task statuses, and critical decisions from a conversation.

When to use it

When starting a feature implementation and needing a concise, trackable plan before writing code.

When not to use it

For trivial modifications or when no prior discussion has taken place.

Examples

Plan for user authentication feature

Create a feature implementation plan for adding user authentication to our existing web app.

Plan from refactoring discussion

Based on our discussion about the refactoring, produce a markdown plan with steps and subtasks.

Plan for payment API integration

Generate a plan document for integrating the new payment API into the backend service.

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.