Dependency Mapping Across Teams for a Roadmap
See what blocks what.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
Map dependencies across roadmap items. Roadmap items with owners: [ROADMAP_ITEMS]. Teams and systems involved: [TEAMS_AND_SYSTEMS]. Known blockers: [KNOWN_BLOCKERS]. Produce a dependency table: Item | Depends on | Type (technical, data, decision, legal, vendor) | Needed by | Owner | Status | Risk if late. Identify the critical chain, circular dependencies, and items with many dependents. Draw a text diagram using arrows. Suggest ways to reduce coupling (interfaces, feature flags, parallel mocks, smaller releases) and a sequencing recommendation with reasons. Add a communication plan with the teams on the critical chain, a weekly dependency check agenda (10 minutes), and a template to request a commitment from another team (80 words). Include a risk rating and what to do when another team cannot commit. Use only my information and mark assumptions. Return the dependency table sorted by the earliest date needed, add a short list of the three dependencies most likely to slip with the reason, and a draft of the message to the team that owns the riskiest one.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.