planning

Generate comprehensive implementation plans with phase-driven design and interface contracts.

181|22|Updated Nov 13, 2025
One-click install
npx skills add https://github.com/markmdev/meridian --skill planning-markmdev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: planning
Source: https://github.com/markmdev/meridian/tree/main/.claude/skills/planning
Command: npx skills add https://github.com/markmdev/meridian --skill planning-markmdev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Claude often struggles with shallow planning for complex tasks, leading to broken implementations and wasted effort. This Skill guides Claude through a rigorous, multi-phase planning process, ensuring deep understanding, thorough design, and explicit integration steps before any code is written, drastically reducing rework.

Core Features & Use Cases

  • Deep Discovery: Utilize subagents to aggressively explore the codebase, trace data/control flows, and verify assumptions, building a solid foundation for the plan.
  • Structured Design & Decomposition: Systematically choose optimal approaches, define clear target states, and break down work into manageable, dependent subtasks.
  • Mandatory Integration Planning: Explicitly plan how multiple modules connect and interact, preventing orphaned components and integration failures in complex systems.
  • Use Case: When starting a new feature that touches multiple services or requires significant architectural changes, use this Skill to ensure Claude thoroughly understands the existing architecture, designs a comprehensive solution, and plans all integration points before writing a single line of code.

Quick Start

Use the planning skill to create a detailed plan for implementing a new user authentication system. Focus on deep discovery of existing auth mechanisms and integration with the current API gateway.

Frequently Asked Questions about planning

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

FAQPage Schema
How do I create a comprehensive implementation plan for a complex software feature?

A comprehensive implementation plan systematically explores your codebase, designs the solution architecture, breaks work into dependent subtasks, and explicitly maps integration points across modules before coding begins. This rigorous approach prevents broken implementations and rework.

When should I plan architecture changes and refactors before starting implementation?

Plan architecture changes and refactors upfront when they touch multiple files, systems, or services. Deep discovery of existing flows, structured decomposition into phases, and mandatory integration planning prevent orphaned components and ensure all connection points work correctly.

How do I decompose complex tasks into manageable subtasks with clear dependencies?

Decomposition breaks work into dependent subtasks by first mapping data and control flows across your codebase, then defining target states and precise file locations, module structure, and interface contracts that guide implementation of each phase.

What's the best way to plan integration points when implementing features across multiple services?

Mandatory integration planning explicitly defines how multiple modules connect and interact. Trace existing architectures, design the solution end-to-end, identify all integration surfaces, and document module dependencies and interface contracts before implementation.

Do I need planning for bug fixes with unclear scope?

Yes. Bug fixes with unclear scope benefit from planning because deep codebase exploration, flow analysis, and decomposition clarify root causes, prevent incomplete fixes, and ensure changes integrate safely without side effects across affected systems.