impact-analyzer
Analyze and document the impact of planned changes.
When & Why to Use This Skill
The impact_analyzer skill is a specialized tool designed to solve the problem of unforeseen regressions and scope creep in software development. It provides a structured framework for performing thorough impact analysis on planned changes, helping developers and architects identify affected system areas, assess technical risks, and define necessary verification steps before implementation. By automating the creation of standardized documentation like IMPACT.md, it ensures that every modification is backed by a clear strategy, enhancing system stability and team alignment.
Use Cases
- Risk Mitigation for Refactoring: Systematically evaluate how restructuring core modules will affect dependent services and legacy components to prevent breaking changes.
- Pre-Implementation Scoping: Define the exact boundaries of new feature development to ensure all affected files, logic paths, and database schemas are accounted for.
- Verification and Test Planning: Identify the specific unit, integration, and regression tests required to validate changes, ensuring high-quality deployments.
- Technical Debt Management: Document the impact of 'quick fixes' to understand long-term architectural implications and maintain a clear audit trail of system evolution.
| name | impact_analyzer |
|---|---|
| description | Analyze and document the impact of planned changes. |
| short-description | Impact analysis |
Purpose
Clarify scope, risks, and verification before changes.
Steps
- Fill
IMPACT.mdwith affected areas and risks. - Identify tests and checks required.
- Link impact notes in
PLANS.md.