Our review
Generates a structured Markdown implementation plan with progress tracking via steps and subtasks.
Strengths
- Produces a clear, minimal, actionable plan
- Includes visual progress tracking with emojis and percentage
- Forces explicit architectural decisions before coding
Limitations
- Does not generate code, only the plan
- Progress must be updated manually
- May require clarifications for complex projects
When you need to formalize a design conversation into a precise action plan before starting implementation.
When the requirement is already well understood and it's more efficient to code directly without a prior plan.
Security analysis
SafeThis is a static markdown template for creating project plans. It contains no executable code, no dangerous commands, and no interaction with external systems. It poses no security risk.
No concerns found
Examples
Create a detailed implementation plan for adding JWT-based user authentication to our Node.js API. Include step-by-step tasks with progress tracking.Write a plan to refactor the PaymentGateway class in our Python service into smaller modules. Use the plan creation stage format with 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%
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.
Create log entries with timestamps
Documentation
Creates timestamped log entries to document discoveries, meetings, code reviews, articles, or significant events. Structures information with a summary, event type, sources, and tags, then saves the file to `docs/log/` with a date-based filename and descriptive slug.