Plan Creation

VerifiedSafe

Produce a structured markdown plan document with progress tracking and status emojis.

Sby Skills Guide Bot
DevelopmentIntermediate
107/28/2026
Claude CodeCopilot
#plan-creation#implementation-plan#task-tracking#markdown-template

Recommended for

Our review

This skill generates a Markdown plan document with emoji-tracked steps and a dynamic overall progress percentage.

Strengths

  • Clear, minimal structure suitable for task tracking.
  • Emoji status indicators for quick visual understanding.
  • Automatic progress percentage at the top of the document.
  • Avoids scope creep by sticking strictly to discussed details.

Limitations

  • Requires a full prior exchange to generate the plan.
  • Critical decisions are limited to those explicitly clarified.
  • No automatic updates after plan creation.
When to use it

Use this skill after a thorough conversation to produce a structured, shareable implementation plan.

When not to use it

Do not use it for trivial projects or when you need a live, updatable plan.

Security analysis

Safe
Quality score75/100

The skill only instructs the AI to generate a markdown plan document. There are no declared allowed-tools, and the content does not involve any execution of commands or handling of sensitive data. It poses no security risk.

No concerns found

Examples

Implement user authentication
Based on our conversation about adding JWT-based authentication, please create a plan document following the Plan Creation Stage template.
Add search feature to blog
Generate an implementation plan for the search feature we discussed. Use the markdown template with emojis and progress tracking.

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