Planning Skill

Generates structured implementation plans for software development tasks.

Updated Nov 17, 2025
One-click install
npx skills add https://github.com/grumps/claude-dotfiles --skill planning-skill
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Planning Skill
Source: https://github.com/grumps/claude-dotfiles/tree/main/skills/planning
Command: npx skills add https://github.com/grumps/claude-dotfiles --skill planning-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creating comprehensive technical plans can be time-consuming and often leads to overlooked details. This skill automates the generation of structured implementation plans, ensuring all aspects of a feature—from requirements and technical approach to testing and deployment—are considered and documented.

Core Features & Use Cases

  • Structured Plan Generation: Creates detailed plans following a predefined format, including overview, requirements, technical approach, implementation steps, testing strategy, deployment checklist, risks, and open questions.
  • Contextual Awareness: Gathers project context using just info to tailor the plan to your specific repository and existing workflows.
  • Best Practices Integration: Incorporates language-specific best practices (e.g., Go error handling, Python type hints, K8s resource limits) into the plan.
  • Use Case: When starting a new feature, use /plan add rate limiting to API. The skill will ask clarifying questions, analyze your project, and generate a complete implementation plan, saving you hours of upfront design work and ensuring a consistent approach.

Quick Start

Ask Claude to "Create an implementation plan for adding a new user authentication module."

Frequently Asked Questions about Planning Skill

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

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

Implementation plans document the complete approach to building a feature. Use the Planning Skill to generate a structured plan including requirements, technical approach, implementation steps, testing strategy, deployment checklist, and risk mitigations. This ensures consistent design decisions and prevents overlooked details before development begins.

What should a technical design plan include?

A technical design plan covers overview, requirements, technical approach, implementation steps, testing strategy, deployment checklist, risks and mitigations, and open questions. The Planning Skill auto-generates this structure, incorporates language-specific best practices, and references your existing project workflows to tailor recommendations to your codebase.

How do I plan for risks and deployment before coding?

Risk management and deployment planning happen upfront in the structured plan. The Planning Skill identifies potential blockers, mitigation strategies, and deployment prerequisites as part of the complete plan, reducing surprises and rework during implementation and release phases.

Can the Planning Skill use my project context?

Yes. The Planning Skill gathers your project context using `just info` to tailor plans to your repository, existing workflows, and tech stack. This produces recommendations aligned with your language, frameworks, and architecture patterns rather than generic guidance.

When should I use implementation planning vs. starting to code?

Use implementation planning before major features, architectural changes, or cross-component work. Planning upfront clarifies requirements, identifies technical blockers, and ensures a consistent approach across your team. It saves hours of rework and design debate during development.