introduce-dependencies-conservatively

What problem does it solve? Teams often add, upgrade, or remove package dependencies casually, leading to bloated installs, version conflicts, private API coupling, and unmaintainable codebases. This Skill enforces a disciplined decision process so every dependency change is justified, scoped, and uses only stable public interfaces. ## Core Features & Use Cases - Structured Dependency Evaluation: Requires an explicit capability statement and reuse analysis across the language, existing code, current dependencies, and ecosystem before adding anything new. - Role Classification and Versioning Rules: Distinguishes required, optional, test, and documentation dependencies, and demands concrete justification for minimum version constraints. - Scoped Change Management: Enforces one semantic dependency change per PR, with checklists and templates for additions, removals, replacements, and upgrades. - Use Case: When adding penalized regression to an R package, the Skill guides you to confirm no existing dependency covers it, select a maintained library like glmnet, call only its public API, and isolate the change in its own PR. ## Quick Start Ask the AI to evaluate whether adding a specific package dependency to your project is justified and to produce the dependency statement and PR scope for the change.