plan

Generate a phased implementation plan with risks and user approval.

Updated Jun 18, 2023
One-click install
npx skills add https://github.com/kuroweb/dotfiles --skill plan-kuroweb
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/kuroweb/dotfiles/tree/main/agents/.cursor/skills/plan
Command: npx skills add https://github.com/kuroweb/dotfiles --skill plan-kuroweb

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill ensures that before any code is written, a thorough and actionable implementation plan is created, reducing ambiguity and potential rework.

Core Features & Use Cases

  • Requirement Clarification: Reconfirms what needs to be built.
  • Risk Identification: Surfaces potential issues and blockers early.
  • Phased Planning: Breaks down implementation into manageable steps.
  • User Approval: Requires explicit confirmation before proceeding.
  • Use Case: When starting a new feature like "real-time market resolution notifications," you can use /plan to get a detailed breakdown of database changes, service implementation, integration points, and frontend components, along with estimated complexity and risks.

Quick Start

Use the plan skill to create a detailed implementation plan for adding real-time market resolution 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 a new software feature?

To create an implementation plan, use a planner agent to clarify requirements, identify risks, and break down work into manageable phases. This approach ensures a comprehensive breakdown of database changes, services, and frontend components before coding begins.

What is the best way to break down ambiguous software requirements into tasks?

Breaking down ambiguous software requirements involves clarifying the project scope and identifying potential blockers early. A structured planning process reconfirms what needs to be built and divides complex implementation into actionable steps with estimated complexity.

Does the planning process require approval before writing code?

Yes, the planning process requires explicit user approval before proceeding to execution. This ensures you review the phased task breakdown, risk assessment, and requirement clarification, preventing potential rework before any actual software development starts.

Can I use this for complex refactoring and architectural changes?

Yes, you can use this for complex refactoring and architectural changes. The planner agent is applicable for structural modifications and ambiguous requirements, generating a comprehensive implementation plan that surfaces integration issues and phases the work.

Why do I need task breakdown and risk assessment for software development?

Task breakdown and risk assessment are needed to reduce ambiguity and potential rework in software development. Identifying blockers early and structuring implementation into phases ensures that database, service, and frontend components are thoroughly planned.