pmx-dependency-mapping

name	pmx-dependency-mapping
description	Map dependencies that affect delivery, adoption, or launch.

Dependency Mapping

When to use

• Use when the task clearly matches this PM activity.
• Use when a structured answer is more useful than a generic brainstorm.
• Use when the user needs explicit trade-offs, implications, or next steps.

Instructions

1. Clarify the goal, user, or decision context.
2. Use the skill-specific lens below to structure the work.
3. Make assumptions explicit instead of hiding them.
4. End with a practical recommendation or next step.

Skill-specific lens

1. List upstream and downstream dependencies.
2. Assess criticality and timing risk.
3. Identify owners and unresolved questions.
4. Recommend sequencing or mitigation.

Output

• Dependencies
• Critical path
• Owners
• Risks
• Mitigations