Our review
This skill generates a Markdown feature implementation plan with step statuses tracked by emojis and an overall progress percentage.
Strengths
- Clear, concise structure with modular steps
- Visual progress tracking via emojis and percentage
- Highlights critical decisions already made during exploration
- Avoids extra scope and keeps integration minimal
Limitations
- Delivers a plan only, not the actual code or implementation
- Accuracy depends on the quality of prior discussion
- Emoji-based statuses may not fit formal project management tools
After exploring a feature in depth, when you need a clear, actionable plan before starting implementation.
For trivial changes that don't need a written plan, or when the scope is still ambiguous and needs further clarification.
Security analysis
SafeThe skill only instructs to produce a markdown plan document based on the conversation. It does not involve any tool usage, network access, or system modification. There is no risk of destructive actions or data exfiltration.
No concerns found
Examples
Based on our full exchange, produce a markdown plan document for implementing JWT authentication, with overall progress, critical decisions, and tasks tracked by emojis.Create a markdown implementation plan for adding pagination to our existing REST API. Keep it minimal and include the TLDR, decisions, and modifiable steps with progress tracking.Generate a feature implementation plan for migrating from MySQL to PostgreSQL. Use the template with overall progress percentage and per-step status emojis.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%
TLDR
Short summary of what we're building and why.
Critical Decisions
Key architectural/implementation choices made during exploration:
- Decision 1: [choice] - [brief rationale]
- Decision 2: [choice] - [brief rationale]
Tasks:
-
[ ] 🟥 Step 1: [Name]
- [ ] 🟥 Subtask 1
- [ ] 🟥 Subtask 2
-
[ ] 🟥 Step 2: [Name]
- [ ] 🟥 Subtask 1
- [ ] 🟥 Subtask 2
...
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.
Next.js App Router Expert
Development
A skill that turns Claude into a Next.js App Router expert.
README Generator
Development
Creates professional and comprehensive README.md files for your projects.
API Documentation Writer
Development
Generates comprehensive API documentation in OpenAPI/Swagger format.