planning

Create step-by-step implementation plans for software features in markdown.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/anthony-fdez/claude-skills --skill planning-anthony-fdez
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: planning
Source: https://github.com/anthony-fdez/claude-skills/tree/main/.claude/skills/planning
Command: npx skills add https://github.com/anthony-fdez/claude-skills --skill planning-anthony-fdez

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill tackles the challenge of ensuring complex features are implemented systematically, preventing missed steps, scope creep, and architectural oversights by creating detailed, actionable plans before coding begins.

Core Features & Use Cases

  • Structured Planning: Guides the creation of comprehensive, step-by-step implementation plans for new features or significant changes.
  • Context Gathering: Facilitates thorough research by reading existing documentation and searching the codebase for relevant information.
  • Use Case: Before starting to build a new user authentication flow, you can use this Skill to generate a detailed plan that outlines database schema changes, API endpoint creation, frontend component development, and necessary security considerations.

Quick Start

Use the planning skill to create an implementation plan for the new user profile editing feature.

Frequently Asked Questions about planning

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

FAQPage Schema
How do I create a step-by-step implementation plan for a new software feature?

To create an implementation plan, you gather context by reviewing documentation and analyzing the codebase, then generate a detailed, self-contained markdown document outlining the step-by-step execution for user approval.

What is the best way to prevent scope creep and missed steps during feature development?

The best way to prevent scope creep during feature development is to map out implementation steps systematically beforehand, ensuring architectural oversights are caught through comprehensive context gathering and structured planning.

How do you analyze a codebase before implementing database schema changes and API endpoints?

Analyzing a codebase before implementing database schema changes involves reading existing documentation and searching for relevant code to guide the creation of a comprehensive, actionable plan.

Can I generate a markdown document for planning complex architectural changes?

Yes, you can generate a self-contained markdown document for planning architectural changes, which facilitates thorough research and outlines necessary steps before coding begins.

Do I need to review existing documentation before mapping out implementation steps?

Yes, reviewing existing documentation is required to gather sufficient context, ensuring the generated implementation plan accurately addresses architectural dependencies and technical constraints.