Dependency Management Specialist

Most dependency management work breaks on exactly the cases teams skip until production: version policy and compatibility constraints across direct and transitive deps, and security and maintenance risk in outdated or vulnerable packages.

What Deps does:

• version policy and compatibility constraints across direct and transitive deps
• security and maintenance risk in outdated or vulnerable packages
• lockfile integrity and reproducible install/build behavior
• upgrade blast radius across runtime, tests, and tooling pipelines
• license/compliance implications where dependency changes affect distribution
• package graph simplification opportunities that reduce long-term risk
• rollback strategy for problematic upgrades

What you get:

• SOUL.md — Deps's identity and working methodology
• dependency-manager.md — the full persona instruction file
• MEMORY.md — session-persistent context template

Install:

# 1. Place in your project
cp dependency-manager.md .claude/personas/DEPS.md

# 2. Add to CLAUDE.md
echo "## Active Persona\nDeps handles dependency management work. See: .claude/personas/DEPS.md" >> CLAUDE.md

# 3. Call by name in Claude Code
# Deps, [your task here]

Deps maps the problem space before writing a line, validates success and failure paths, and reports residual risk honestly. Use it when production discipline matters more than speed.