plan

Generates step-by-step plans for implementing software changes with risk assessment.

1|1|Updated Feb 1, 2026
One-click install
npx skills add https://github.com/corbat-tech/coco --skill plan-corbat-tech
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/corbat-tech/coco/tree/main/.claude/skills/plan
Command: npx skills add https://github.com/corbat-tech/coco --skill plan-corbat-tech

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill prevents premature coding by ensuring a thorough understanding of requirements, potential risks, and a clear, actionable implementation strategy before any code is written.

Core Features & Use Cases

  • Requirement Clarification: Restates user requests to ensure alignment.
  • Codebase Exploration: Analyzes existing code to identify affected files and patterns.
  • Phased Planning: Breaks down complex features into manageable implementation steps with risk assessments.
  • User Confirmation Gate: Requires explicit user approval before proceeding with code generation.
  • Use Case: Before adding a new authentication method, use /plan add a new authentication method to get a detailed breakdown of affected files, implementation phases, and potential risks, ensuring a robust and well-considered approach.

Quick Start

Use the plan skill to outline the steps for refactoring the user authentication module.

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 complex software feature?

Creating an implementation plan involves analyzing software requirements and exploring the existing codebase to identify affected files. The process breaks down complex development tasks into phased, actionable steps with risk assessments before any code generation begins.

What is the best way to assess risks before refactoring a codebase?

Risk assessment during codebase refactoring is handled by analyzing existing code patterns and identifying affected files. This generates a phased implementation strategy that highlights potential risks and requires explicit user confirmation before proceeding with modifications.

How do I break down agile project management tasks into actionable steps?

Breaking down agile project management tasks involves restating user requests for alignment and exploring the codebase. This produces a detailed, phased plan that defines testing strategies and actionable implementation steps for the development workflow.

Can I require user confirmation before code generation modifies my files?

Yes, requiring user confirmation before code generation is a core feature of the planning process. This confirmation gate ensures explicit user approval is granted for the implementation strategy and risk assessment before any code modification occurs.

When do I need a phased implementation strategy for software development?

A phased implementation strategy is needed when adding complex features like a new authentication method to an existing codebase. It ensures a robust approach by identifying affected files, defining testing strategies, and assessing risks before coding starts.