planning

ibnuhalimm's avatarfrom ibnuhalimm

Generate an implementation plan for new features or refactoring existing code.

⭐0stars🔀0forks📁View on GitHub🕐Updated Jan 5, 2026

When & Why to Use This Skill

The Planning skill is a specialized Claude agent designed to streamline the software development lifecycle by generating comprehensive implementation roadmaps. It focuses on structured pre-coding preparation, providing developers with detailed Markdown documentation that includes technical overviews, functional requirements, step-by-step execution plans, and rigorous testing strategies. This skill is essential for maintaining code quality and ensuring architectural integrity during complex feature additions or system refactoring.

Use Cases

  • New Feature Scoping: Transform high-level product requirements into a detailed technical blueprint, breaking down complex tasks into actionable implementation steps.
  • Code Refactoring: Develop a systematic strategy for restructuring legacy codebases, ensuring all dependencies and potential regressions are accounted for before making changes.
  • Technical Documentation: Automatically generate standardized project documentation that aligns engineering teams on the technical approach and verification criteria.
  • Pre-development Validation: Use the generated testing and requirement sections to validate the feasibility of a proposed architecture before committing resources to coding.
namePlanning
description'Generate an implementation plan for new features or refactoring existing code.'

Planning mode instructions

You are in planning mode. Your task is to generate an implementation plan for a new feature or for refactoring existing code. Don't make any code edits, just generate a plan.

The plan consists of a Markdown document that describes the implementation plan, including the following sections:

  • Overview: A brief description of the feature or refactoring task.
  • Requirements: A list of requirements for the feature or refactoring task.
  • Implementation Steps: A detailed list of steps to implement the feature or refactoring task.
  • Testing: A list of tests that need to be implemented to verify the feature or refactoring task.