The prompt
Score 10 of 10, Excellent
Use it when Several teams or suppliers must hand work to each other, and you need to see who is waiting on whom, by when, and which hand-offs could sink the date.
- {{project_and_deadline}}
- {{teams}}
- {{audience}}
- {{source_notes}}
Full prompt and why it works
Prompt
Project and key deadline: {{project_and_deadline}} Teams, suppliers and their contacts: {{teams}} Who will use the map: {{audience}} Plans, notes and messages that mention what each team needs from the others: """ {{source_notes}} """ Task: Map the dependencies between the teams above, for {{audience}}, so that every hand-off has a named giver, receiver and date, and the ones that threaten the deadline are visible early. Format: 1. Dependency table with the columns ID, What is needed (a specific deliverable, decision or approval), From (team giving it), To (team waiting), Needed by, Promised by, Gap (calendar days, promised minus needed; a positive number means late), Status (Agreed, Not yet agreed, At risk), Source. 2. Critical hand-offs: dependencies on the chain that leads to the deadline, or where a slip would block more than one team, with one sentence each on why. 3. Missing agreements: where the receiving team assumes something the giving team has not confirmed. 4. Teams waiting on each other: any circular dependencies. 5. Next steps: up to 5, each a specific conversation or confirmation between named teams. Requirements: - Map only dependencies in the notes; do not add ones you think are likely. If a hand-off seems to be missing (testing with no mention of a test environment, say), list it as a question, not a dependency. - Dates exactly as given, or "Not stated". Calculate a gap only where both dates exist. - Under 400 words outside the table. Example of one row's form only, with invented content: "DP-03 | Signed-off data fields | Finance | IT | May 9 | May 16 | 7 | At risk | Email from IT, Apr 28" If two sources give different dates for the same hand-off, use the later one in the table and note the conflict.
Variables
- {{project_and_deadline}}
- For example "new payroll system, live for the January 1 pay run".
- {{teams}}
- Each team or supplier and its contact, for example "HR (Dana), IT (Lee), Finance (Omar), vendor (account manager)".
- {{audience}}
- For example "the steering group" or "the team leads at Monday's meeting".
- {{source_notes}}
- Plans, notes and messages about what each team needs, with dates and authors.
Why it works
- Format. Every hand-off gets a giver, a receiver, a needed-by and a promised-by date, so the gap between them is a number rather than a feeling.
- What to avoid. Only dependencies in the notes are mapped; likely gaps come back as questions, so the map does not invent commitments.
- If unsure. Conflicting dates are noted and the later one is used, which errs toward warning you early.