Our review
This skill generates a structured Markdown plan document with clear steps, status emojis, and progress tracking.
Strengths
- Emojis provide clear task status at a glance
- Includes automatic progress percentage calculation
- Encourages explicit critical decisions
- Minimal and reproducible template
Limitations
- Requires prior exchange to capture context
- Progress tracking is not dynamic without manual updates
- May become verbose for very complex projects
When breaking down a feature or change into actionable steps before development begins.
For trivial changes or when the plan is already obvious without documentation.
Security analysis
SafeThe skill only instructs the AI to produce a markdown plan based on conversation, with no execution of tools or external actions.
No concerns found
Examples
Based on our discussion about adding user authentication, create a detailed plan with progress tracking.Given our exchange on refactoring the payment module, produce a step-by-step plan with status emojis.From our conversation about the login bug, generate a plan document outlining the fix steps and critical decisions.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.
bkend.ai Operational Guides
Documentation
Provides operational guides for bkend.ai, including troubleshooting, migration steps, performance optimization, and platform comparisons (vs Firebase, Supabase). Use when you need to resolve common errors, understand best practices, or decide between backend services.