planning-methodology

Create reversible implementation plans with risk assessment and verification steps.

206|32|Updated Jul 25, 2025
One-click install
npx skills add https://github.com/VAMFI/claude-user-memory --skill planning-methodology-vamfi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: planning-methodology
Source: https://github.com/VAMFI/claude-user-memory/tree/main/.claude/skills/planning-methodology
Command: npx skills add https://github.com/VAMFI/claude-user-memory --skill planning-methodology-vamfi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures that all code changes are surgical, safe, and easily reversible. It transforms high-level requirements and research into a detailed, executable blueprint, minimizing risks and maximizing clarity before any code is written.

Core Features & Use Cases

  • Minimal Change Analysis: Identifies the smallest set of modifications required, preferring extension over alteration to reduce blast radius.
  • Comprehensive Risk Assessment: Proactively identifies potential breaking changes, performance issues, and security vulnerabilities, providing clear mitigations.
  • Detailed Rollback Plans: Every plan includes exact commands and verification steps to safely undo changes, ensuring peace of mind.
  • Use Case: After researching how to integrate Redis caching, Claude uses this Skill to generate a plan that outlines specific file changes, step-by-step implementation, a test plan, potential risks, and a clear rollback strategy, ensuring a smooth and safe deployment.

Quick Start

Plan adding Redis caching to ProductService

/plan Add Redis caching to ProductService with 5-min TTL

Frequently Asked Questions about planning-methodology

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

FAQPage Schema
How do I plan code changes to minimize risk and ensure they're reversible?

Planning methodology creates minimal-change, reversible implementation plans by analyzing requirements, assessing risks, and structuring incremental steps with rollback procedures. This approach identifies the smallest modifications needed, proactively surfaces breaking changes and security concerns, and provides exact commands to safely undo changes if needed.

What's the best way to transform requirements into a detailed, executable implementation blueprint?

Start with codebase discovery to understand current architecture, then perform risk assessment to identify potential vulnerabilities and performance issues. Structure implementation as verified incremental steps, documenting rollback commands for each stage to ensure changes remain surgical and safe throughout deployment.

How do I identify the smallest set of code changes needed for a feature?

Minimal change analysis prioritizes extension over alteration to reduce blast radius and side effects. By mapping dependencies and examining existing patterns, you determine only the necessary modifications, avoiding unnecessary refactoring that increases risk and complexity.

Can I plan complex features or refactors without breaking existing functionality?

Yes. Comprehensive risk assessment proactively identifies potential breaking changes, performance degradation, and security vulnerabilities before implementation. Detailed rollback plans with verification steps at each phase enable safe reversibility and recovery if issues arise during or after deployment.

What should I include in a deployment plan to handle unexpected issues?

Include exact rollback commands, verification steps, risk mitigations, and a test plan that validates each incremental change. Structured sequencing with codebase discovery and risk awareness ensures every phase is reversible, allowing rapid recovery if problems are detected.