Our review

Generates a structured Markdown implementation plan with progress tracking and emoji status indicators.

When to use it

When you need to formalize an implementation plan after exploring options with the agent.

When not to use it

If a plan already exists or the task is trivial and doesn't need structuring.

Examples

Feature Implementation Plan

Based on our discussion about adding dark mode to the app, create a plan document with steps, status emojis, and progress percentage.

Refactoring Plan

Produce a plan for refactoring the authentication module following the decisions we made. Include tasks, subtasks, and status tracking.

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.