create-plan

Create comprehensive implementation plans with phased steps and validation.

5|3|Updated Oct 23, 2025
One-click install
npx skills add https://github.com/Cygnusfear/claude-stuff --skill create-plan-cygnusfear
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-plan
Source: https://github.com/Cygnusfear/claude-stuff/tree/main/skills/create-plan
Command: npx skills add https://github.com/Cygnusfear/claude-stuff --skill create-plan-cygnusfear

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Creating comprehensive, high-quality implementation plans is a time-consuming yet critical task for successful project execution. This skill guides the creation of detailed plans, ensuring all necessary sections, compliance checks, and removal specifications are included.

Core Features & Use Cases

  • Structured Plan Generation: Creates detailed plans for features, refactors, or fixes with required sections like Context, Impact Analysis, and Implementation Steps.
  • CLAUDE.md & Type Compliance: Ensures adherence to project-specific naming, architecture, and type requirements, promoting consistency.
  • Critical REMOVAL SPECIFICATION: Guides the explicit listing and verification of old code that must be removed, preventing technical debt.
  • Use Case: After an architectural analysis, use this skill to create a detailed refactoring plan, outlining every step, affected file, and old code to be removed, ensuring a clean and well-managed transition.

Quick Start

Choose a descriptive plan name

PLAN_NAME="implement-user-authentication"

Create the plans directory

mkdir -p .plans

Review relevant CLAUDE.md files

cat CLAUDE.md

Frequently Asked Questions about create-plan

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

FAQPage Schema
How do I create a detailed implementation plan for a feature or refactor?

An implementation plan structures your work into phases with clear steps, dependencies, and validation points. This skill generates comprehensive plans in a .plans/ directory, covering context, impact analysis, affected files, removal specifications, and phased implementation guidance to ensure nothing is missed.

What should a good implementation plan include?

A complete implementation plan includes original requirements extraction, architecture compliance checks, naming conventions, file listings, explicit removal specifications for old code, phased implementation steps, and validation criteria. This ensures technical debt is eliminated and transitions are clean.

How do I ensure my plan follows project conventions and type requirements?

Review your project's CLAUDE.md file for naming, architecture, and type standards before plan generation. This skill validates adherence to those conventions and ensures consistency across your codebase during implementation.

Can I use implementation plans for bug fixes as well as features?

Yes. Implementation plans work for features, refactors, and bug fixes. The skill structures each by analyzing requirements, mapping affected files, specifying code removal, and breaking work into actionable phases with clear validation steps.

Why is removal specification critical in an implementation plan?

Explicit removal specifications prevent technical debt by forcing you to catalog and verify old code that must be deleted. This prevents orphaned or conflicting code from lingering and ensures a clean transition after implementation completes.