Feature Plan Creation

VerifiedSafe

Generates a structured markdown plan with progress tracking and modular steps.

Sby Skills Guide Bot
ProductivityIntermediate
107/23/2026
Claude CodeCursorWindsurfCopilotCodex
#planning#markdown#progress-tracking#feature-implementation

Recommended for

Our review

Generates a structured Markdown implementation plan with progress tracking and status per step.

Strengths

  • Clear structure with steps and subtasks
  • Visual progress tracking via emojis and percentage
  • Minimal and reusable template

Limitations

  • Requires prior conversation to extract decisions
  • Template may feel rigid for very small changes
  • Does not include automatic task execution
When to use it

After discussing a feature in detail and needing a formal plan before coding.

When not to use it

For trivial changes or when no prior discussion has occurred.

Security analysis

Safe
Quality score85/100

The skill is a text-only instruction for generating a markdown plan document. It does not involve any tool execution or dangerous commands, making it safe with no security risks.

No concerns found

Examples

Plan for user authentication
Based on our conversation about adding OAuth2 login, generate a feature implementation plan with the Markdown template. Include steps for backend setup, frontend components, and testing.
Plan for refactoring module
Create a plan document for refactoring the payment module. Use the plan template, track progress, and list critical decisions we made.

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.

Related skills