deep-plan

Generate a detailed implementation plan with phases and slices in plan.md.

10|1|Updated Mar 4, 2026
One-click install
npx skills add https://github.com/Sungmin-Cho/claude-deep-work --skill deep-plan-sungmin-cho
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deep-plan
Source: https://github.com/Sungmin-Cho/claude-deep-work/tree/main/skills/deep-plan
Command: npx skills add https://github.com/Sungmin-Cho/claude-deep-work --skill deep-plan-sungmin-cho

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps engineering teams produce a detailed, traceable implementation plan for complex software tasks, aligning stakeholders and guiding execution.

Core Features & Use Cases

  • Phase-driven planning (Brainstorm/Research/Plan/Implement/Test) with guardrails and template-backed sections to ensure thorough preparation.
  • Slice-based work units with checklists, tests, and risk considerations to support incremental delivery.
  • Support for zero-base or existing-project contexts to tailor the plan to current work.

Quick Start

Describe the task and run the plan phase to generate plan.md.

Frequently Asked Questions about deep-plan

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

FAQPage Schema
What is phase-driven planning and how does it structure software implementation?

Slice-based implementation planning divides complex tasks into slice-level work units with checklists and tests. Each slice supports incremental delivery and maintains traceability from planning decisions to execution requirements.

How do I integrate TDD checklists into my project management workflow?

Yes, the planning template supports both zero-base and existing-project contexts. It tailors the generated plan.md to your current work environment, ensuring the phase management and slice execution fit your project state.

What is the best way to break down a large software task into executable slices?

Yes, the planning approach integrates TDD by enforcing testability within the plan. Slice-based work units include specific test considerations and checklists, ensuring traceability from implementation requirements to test execution.

Why does my software implementation plan lack traceability from design to execution?

The best way to break down a large task is using slice-based work units with defined checklists and risk considerations. This method supports incremental delivery and produces traceable execution requirements within a plan.md file.

Why does my software implementation plan lack traceability from design to execution?

Implementation plans lack traceability when phase-driven workflows and guardrails are missing. Using a template-backed plan.md ensures decisions trace directly to execution requirements and slice-level checklists.