deep-plan

Plan and execute multi-file code changes with documented iterative refinement.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill provides a disciplined process to prevent wasted effort by separating planning from execution, ensuring thorough understanding before coding begins.

Core Features & Use Cases

  • Research & Analysis: Deeply analyze codebases to produce detailed findings for accurate understanding.
  • Structured Planning: Generate comprehensive implementation plans with code snippets, file modifications, and trade-offs.
  • Iterative Annotation: Incorporate user feedback directly into plans through inline annotations for refinement.
  • Task Breakdown & Execution: Decompose plans into atomic tasks and execute them systematically with progress tracking.
  • Use Case: Ideal for developers performing complex feature migrations or refactors, where architecture decisions must be examined and validated carefully.

Quick Start

Invoke /deep-plan to begin the workflow, then follow the guided phases to research, plan, annotate, and implement.

Frequently Asked Questions about deep-plan

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

FAQPage Schema
How do I plan complex multi-file code changes before execution?

To plan complex multi-file code changes, you need a structured workflow that separates research from execution, analyzing the codebase deeply to produce detailed findings and comprehensive implementation plans before any coding begins.

What is the best way to break down a large software refactoring project into tasks?

Breaking down a large software refactoring project requires decomposing comprehensive implementation plans into atomic tasks, executing them systematically while tracking progress, and validating architecture decisions iteratively before writing code.

Can I incorporate feedback into implementation plans for feature migrations?

You can incorporate feedback into implementation plans for feature migrations through iterative annotation, allowing user input to refine code snippets, file modifications, and trade-off assessments directly within the plan.

Does this workflow support analyzing existing codebases for architecture decisions?

Yes, this workflow supports analyzing existing codebases for architecture decisions by deep-diving into the code to produce detailed research findings, ensuring thorough understanding and explicit documentation are reviewed before execution.

When should I use a structured AI workflow for project management?

You should use a structured AI workflow for project management when performing complex feature migrations or refactors, preventing wasted effort by ensuring all architecture decisions and trade-offs are examined and validated carefully.

Why separate planning from execution in software development?

Separating planning from execution in software development prevents wasted effort by ensuring thorough understanding of the codebase, explicit documentation of trade-offs, and continuous validation of complex changes before implementation begins.