Dependency Conflict Resolver Skill

Untangle "could not resolve dependency" hell into a clear, ranked plan.

Working from a brief

Infer the package manager and ecosystem from the error or files mentioned; label assumptions (assumed — confirm). Always deliver a concrete resolution path even from just the error text.

Input

Ask for these if not provided:

• The install error — the conflict output exactly as the tool printed it
• The manifest — package.json, requirements.txt, go.mod, pom.xml, whichever applies
• The lockfile — if one exists, since it is usually where the conflict is pinned
• The package manager — npm, pnpm, yarn, pip, Maven, Go modules; infer what's missing

Output Structure