
Cross-Functional Dependency Mapper
Map cross-functional dependencies and identify critical path to prevent project delays
What You Can Do
You can systematically identify which teams must complete work before others can start, pinpoint the critical path that determines your actual end date, and create sequencing plans that prevent bottlenecks. This skill reveals invisible dependencies—like why marketing can't plan assets until engineering confirms the launch date—and helps you communicate realistic timelines to stakeholders based on actual workflow constraints, not optimistic assumptions.
Features
uncover hidden blockers between functions that cause cascading delays
identify the sequence of work that determines your project end date
create realistic work order that minimizes idle time and parallel opportunities
document exactly what each team needs from others before they can start
generate clear explanations for why timelines are compressed or why parallel work isn't possible
flag when multiple teams compete for shared resources or reviews
understand how delays in one function cascade across dependent teams
Example Output
Input: You're launching a SaaS feature with product, design, engineering, marketing, QA, and operations teams.
Output:
Critical Path Identified:
- Product requirements finalized (Week 1)
- Design mockups complete (Week 2–3) — blocked by #1
- Engineering development (Week 4–6) — blocked by #2
- QA testing (Week 7) — blocked by #3
- Marketing launch prep (Week 6–7) — can start parallel to QA, blocked by final feature list
- Operations runbook (Week 7) — blocked by QA sign-off
Bottleneck: Design review (single stakeholder) delays engineering by 3 days. Adding a second reviewer unblocks 1 week.
Sequencing recommendation: Start marketing assets in Week 5 using design concepts (not final designs) to reclaim launch timeline.
What's Included
- SKILL.md instruction file with dependency mapping framework:
- Cross-functional dependency matrix template (teams × tasks × blockers):
- Critical path worksheet with sequencing logic:
- Stakeholder communication template for timeline justification:
- Resource conflict detection checklist:
Who It's For
- Project managers coordinating 3+ cross-functional teams on product launches or feature releases
- Product leaders managing timelines across design, engineering, and marketing dependencies
- Operations managers preventing delays in complex workflows with handoff points
- Scrum masters or agile coaches working with distributed or siloed teams
- Executive stakeholders needing realistic timelines based on actual dependency constraints
Best For
- Product launch planning with compressed timelines
- Feature release sequencing across engineering and design teams
- Identifying why projects can't start in parallel (unblocking false assumptions)
- Re-planning after delays to understand ripple effects across teams
- Communicating realistic timelines to leadership and stakeholders







