skills.rest
samhvw8
samhvw8COMMUNITY
Explore all skills by this author →
GitHub

planning-methodology

Produce detailed technical implementation plans with phased documents and actionable outputs.

14|3|Updated Jun 24, 2021
Search Tags:#planning#architecture#rollback#software development#implementation#strategy#risk management
One-click install
npx skills add https://github.com/samhvw8/dotfiles --skill planning-methodology
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: planning-methodology
Source: https://github.com/samhvw8/dotfiles/tree/main/dot_claude/skills/planning-methodology
Command: npx skills add https://github.com/samhvw8/dotfiles --skill planning-methodology

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Implementing new features or changes without a clear, systematic plan can lead to increased risk, unexpected side effects, and difficult rollbacks. This Skill provides a robust methodology for creating implementation plans that are minimal-change, fully reversible, and include clear verification steps, ensuring safe and predictable development.

Core Features & Use Cases

  • Minimal Change Analysis: Identify the smallest set of changes required, preferring extension over modification and new files over existing ones.
  • Risk Assessment & Mitigation: Proactively identify potential breaking changes, performance issues, and security risks, with detailed mitigation and contingency plans.
  • Incremental Implementation Sequence: Order work steps for safety, with tests alongside and clear verification checkpoints at each stage.
  • Use Case: A new caching layer needs to be added to a critical service. This Skill generates a plan detailing file changes, step-by-step implementation, a comprehensive test plan, identified risks with mitigations, and a precise rollback procedure, ensuring the change is deployed with minimal disruption.

Quick Start

This skill is often auto-invoked when implementation planning is needed.

You can also explicitly request a plan:

"Create an implementation plan for adding Redis caching to the ProductService."

"How should we implement the new user profile feature?"

Frequently Asked Questions about planning-methodology

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

FAQPage Schema
How do I create an implementation plan that minimizes risk and ensures rollback capability?▼

Implementation planning identifies the smallest set of changes required, orders work for safety with verification checkpoints, and includes detailed rollback procedures. This approach ensures changes are reversible and predictable, reducing unexpected side effects and breaking changes in feature development and system design.

What should an implementation plan include for feature development?▼

A comprehensive implementation plan covers file changes, step-by-step task sequencing, test strategies, risk identification with mitigations, contingency procedures, security considerations, and maintainability guidance. Plans are delivered as plan.md files or phased documents in a plans directory structure with actionable trade-off analysis.

How do I identify risks and plan mitigations before implementing architectural changes?▼

Risk assessment proactively surfaces potential breaking changes, performance issues, and security risks across your codebase. Planning methodology structures mitigation strategies and contingency steps for each identified risk, enabling safer deployment of architectural changes and critical service modifications.

Can I use implementation planning for roadmapping and architecture evaluation across teams?▼

Yes. Implementation planning applies to feature planning, architecture evaluation, and roadmapping across codebases and teams. It covers research, design, and task-breakdown scenarios, providing a systematic methodology for aligning technical work with strategic goals and team coordination.

What's the difference between modifying existing files versus creating new ones in a plan?▼

Implementation planning prefers extension over modification and new files over existing ones—a minimal-change approach that reduces blast radius. This preference appears in the detailed change analysis and helps preserve system stability while introducing new functionality like caching layers or service enhancements.

When should I request an implementation plan before starting development work?▼

Request an implementation plan for any feature requiring architectural changes, integration with critical services, or modifications affecting multiple systems. Planning is essential when rollback capability, risk mitigation, and team coordination matter—avoiding costly rework and production incidents.

Related Skills

Explore More Software Engineering Skills→
XGanQAQXGanQAQ
1

create-architecture

Translate approved GDDs into engine-aware architecture maps and API boundaries.

Community
Advanced
GeargrindadminGeargrindadmin

deployment-procedures

Guide safe production deployment workflows with rollback strategies and verification.

Community
Intermediate
CHNISamCHNISam

executing-plans

Automate staged execution of project plans with review checkpoints and batch processing.

Community
Advanced
vasilyu1983vasilyu1983
73

software-architecture-design

Design system-level software architectures including patterns, scalability, resilience, and ADR-driven decisions.

Community
Advanced