Our review

Generates a markdown implementation plan with progress tracking and task statuses.

When to use it

Use this skill to formalize a feature plan after an exploratory discussion.

When not to use it

Do not use it when you need direct implementation or a very detailed plan with time dependencies.

Examples

Feature plan for user authentication

Create a plan document for implementing user authentication with JWT, including progress tracking and task statuses.

Plan for API rate limiting

Generate a feature plan for adding rate limiting to the API endpoints, with steps and subtasks.

Refactoring plan with progress

Produce a plan to refactor the payment module into a microservice, with overall progress percentage.

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.