plan

Generate implementation plans with requirements, risks, and phased steps.

Updated Feb 10, 2026
One-click install
npx skills add https://github.com/ihj04982/my-cursor-settings --skill plan-ihj04982
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/ihj04982/my-cursor-settings/tree/main/skills/plan
Command: npx skills add https://github.com/ihj04982/my-cursor-settings --skill plan-ihj04982

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the process of creating detailed implementation plans, ensuring all requirements are understood, risks are identified, and steps are clearly defined before any code is written.

Core Features & Use Cases

  • Requirement Restatement: Clarifies project goals.
  • Risk Assessment: Identifies potential blockers and challenges.
  • Step-by-Step Planning: Breaks down complex tasks into manageable phases.
  • Use Case: When starting a new feature like real-time notifications, use /plan to get a structured approach covering database changes, service implementation, and frontend integration.

Quick Start

Use the plan skill to create an implementation plan for adding real-time notifications.

Frequently Asked Questions about plan

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create an implementation plan for complex software development tasks?

To create an implementation plan, you need to restate project requirements, assess potential risks, and outline step-by-step phases. This approach breaks down complex architectural changes or refactoring into a structured roadmap before code execution begins.

What is the best way to assess project risks before starting development?

Assessing project risks involves identifying potential blockers and challenges during the requirement clarification phase. Generating a structured implementation plan ensures all risks are documented and mitigated before any actual coding or architectural changes occur.

How do I break down a new feature requirement into manageable development phases?

Breaking down requirements involves restating project goals and outlining step-by-step phases for each component, such as database changes, service implementation, and frontend integration. This creates a structured roadmap for complex software development tasks.

Can I use this implementation planning approach for complex code refactoring?

Yes, implementation planning supports complex refactoring by providing a structured roadmap. It restates the refactoring requirements, identifies potential risks, and breaks the process into manageable phases, awaiting your confirmation before execution.

When do I need a structured roadmap for project initiation?

A structured roadmap is needed when starting new features or architectural changes that require clear requirement definition and risk assessment. It ensures all development phases are defined and potential blockers are identified before coding starts.

Does implementation planning automatically execute code generation after outlining steps?

No, implementation planning does not automatically execute code generation. It generates a comprehensive roadmap and awaits your explicit confirmation before proceeding with any software development or architectural changes.