Dependency Upgrade Impact Brief

Turn scattered inputs into a review-ready Dependency Upgrade Impact Brief.

Important work should not start with an ungrounded chat prompt. Dependency Upgrade Impact Brief gives Software Engineering and Platform Teams a repeatable way to turn authorized source material into a structured decision pack: evidence is labeled, open questions remain visible, and every next step has an accountable human owner.

What you can produce

• Upgrade impact matrix
• affected components and API-change register
• test and rollout checklist
• rollback and owner decision log

The before-and-after

Before: Important context lives across notes, drafts, spreadsheets, messages, policies, or interviews. Teams debate what is known, what is assumed, and who needs to decide.

After: You have a shared, review-ready artifact centered on Upgrade impact matrix, with explicit inputs, trade-offs, missing evidence, and an approval-ready next step.

Why this skill earns a place in your workflow

It converts manifests, lockfiles, changelogs, and architecture notes into traceable impact hypotheses, validation questions, and staged human decisions rather than generic upgrade advice.

Use it when

• You need to convert buyer-provided context into a reusable operating artifact.
• You want assumptions, unknowns, and contradictory inputs surfaced before a team acts.
• You need one clear version of the work for cross-functional review and accountable approval.

How it works

1. Provide the authorized context, goal, constraints, and decision owner.
2. Run the workflow to build an evidence ledger, required deliverables, options, and open questions.
3. Review the output with the accountable human, verify claims, and decide whether to implement the next step.

Built for thoughtful teams, not autopilot

This is an instruction-only SKILL.md workflow. It does not log in, browse private systems, edit records, send messages, publish content, run commands, or execute transactions. It is designed to improve the quality and repeatability of team thinking—not to bypass ownership or professional judgment.

Known limitations

Use only buyer-supplied artifacts; produce hypotheses and checklists, never modify repositories, execute tests, approve changes, or claim security or compliance outcomes. Buyers must verify facts, follow their own policies, and obtain any specialist review required for their context. This skill does not provide legal, financial, privacy, compliance, security, accessibility, or safety determinations.