Our review
Creates a structured Markdown plan document from a conversation, with progress tracking and steps.
Strengths
- Clear structure with steps and subtasks
- Visual progress tracking via emojis and percentage
- Minimal and avoids unnecessary complexity
Limitations
- Requires a detailed prior conversation
- Progress tracking is not dynamic (manual state)
- Does not generate code automatically
When a feature or project needs a precise plan before implementation.
For trivial tasks or those already well understood without documentation needs.
Security analysis
SafeThe skill only instructs the agent to generate a markdown plan document; it does not involve any execution of code, system tools, or network operations, and there are no declarations of tools that could be misused.
No concerns found
Examples
Based on our discussion about adding user authentication, create a plan document with steps and progress tracking.Create a plan for refactoring the payment module following the template, with steps and subtasks.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.
API Documentation Generator
Documentation
Automatically generates OpenAPI/Swagger API documentation.
Technical Writer
Documentation
Writes clear technical documentation following top style guides.
Document Update
Documentation
Align technical documents with actual code implementation and correct documentation drift. Use when updating docs to match current behavior.