Write a dependency agreement with another team
A clear, mutually agreed commitment for work another team must deliver to you, with dates, quality, and escalation.
The prompt
Help me write a dependency agreement with another team whose work my project relies on.
What I need from them: [DELIVERABLE - e.g. "an API endpoint for order status"]
When I need it and why: [DATE, and what slips if it is late]
What "done" means for me: [quality, format, environment, documentation, test data]
Their priorities and constraints: [what I know about their roadmap and capacity]
What I can give them in return: [early specs, testing help, people, flexibility on dates]
Who owns it on each side: [NAMES or roles]
Write a short agreement both teams can sign off on, covering:
- The deliverable and acceptance criteria, in testable terms.
- Key dates, including interim checkpoints (spec agreed, first drop, final).
- What each side commits to, including my inputs to them.
- How we will track status and how often.
- An early-warning rule (e.g. "either side flags a likely slip of more than 3 days within 24 hours").
- The escalation path if we cannot resolve something.
- How changes to the agreement are made.
Rules: keep it collaborative, not contractual in tone - this is two teams in the same organization. Do not invent dates; use [CONFIRM] where I am unsure.
Return:
1. The agreement (one page).
2. A short message proposing it to the other team's lead.
3. The 3 points they are most likely to push back on, and how I could respond.
Highlighted [brackets] are blanks to replace with your own details.
Fill in the blanks and use this promptMore Projects & Operations prompts
What to fill in
- DELIVERABLE - e.g. "an API endpoint for order status"
- DATE, and what slips if it is late
- quality, format, environment, documentation, test data
- what I know about their roadmap and capacity
- early specs, testing help, people, flexibility on dates
- NAMES or roles
- CONFIRM
How this prompt is built
This prompt follows the Few-Shot structure (Few-shot prompting). A few-shot prompt includes one or more worked examples of the input and the output you want, so the model can copy the pattern instead of guessing it.
Related prompts
- Price and document a change order before doing extra workA change order with cost breakdown, schedule impact, and justification that the owner or GC can approve quickly.
- Write an after-action report and improvement planAn after-action report that rates performance against each objective, finds root causes, and produces a tracked improvement plan.
- Write a control plan for a production processA control plan that turns my product and process characteristics into what to check, how, how often, and what to do when it fails.
- Prepare a PPAP submission package for my customerA checklist of every PPAP element at my submission level, the status of each, and a plan to close gaps before the due date.