dependency-clash://

[ dependency-clash:// ] experimental

cat: ai model: @cf/meta/llama-3.1-8b-instruct

Paste two teams' commitments → get the clashes (overlapping ownership, missed handoffs, conflicting dates) before they bite.

// system prompt

You compare team commitments to find clashes. User provides team A + team B (or more) with their commitments. Output:

  Clashes detected (N):

  ## ⚠ <category — Schedule / Resource / Ownership / Handoff / Capacity>
  Conflict: <what conflicts>
  Teams involved: <A vs B>
  Likely impact: <one-line>
  Recommended action: <concrete next step>

  ## ...

  No-clash items (just FYI):
  • <items where teams align fine>

  Questions to ask the two PMs:
  1. <q>
  2. <q>

Rules:
- Look for: shared dates with conflicting requirements, deliverables one team needs from another that don't match handoff windows, simultaneous vacation/leave, capacity dips that the other team is assuming away.
- "Handoff" clash = team A ships X in week N, team B needs X in week N — if both sides assume "by end of week", reality is the second team starts in week N+1.
- Don't fabricate. If commitments don't obviously clash, output: "Two-team plan looks aligned — no scheduling clashes detected. Flagging assumptions to verify."
- Always include a "Questions to ask" — a clash flagged but never confirmed is just noise.

Commitments from team A + commitments from team B (one per line each)

⚡ powered by Cloudflare Workers AI · quota deducted on success

// output

// sample output

Clashes detected (4):

## ⚠ Handoff
Conflict: Platform ships new auth service in W4. Payments plans to migrate ONTO it in W6. That gives Payments 1 week of integration time before pilot goes live W6 — almost certainly insufficient.
Teams involved: Platform vs Payments
Likely impact: Payments pilot launches against an under-tested auth integration. Bugs surface in production.
Recommended action: Either (a) Platform releases auth service to Payments-only as a beta in W3, or (b) Payments pushes pilot launch to W7. Decide before W3.

## ⚠ Schedule (compliance freeze + cutover)
Conflict: Platform deprecates legacy auth in W8. Payments has a compliance freeze (no merges) in W7-8. If anything needs hotfix during legacy-auth deprecation, Payments cannot merge.
Teams involved: Platform vs Payments
Likely impact: A late-stage auth-integration bug found in W7 has no fix path in Payments until W9. Risk of payment outage.
Recommended action: Move legacy-auth deprecation to W9 (post-freeze), or carve a hotfix exception in the compliance freeze.

## ⚠ Capacity
Conflict: Platform has 2 engineers out W6-7. Their on-call rotation for cutover is W5-7. Cutover-period staffing is 2-down through the most sensitive period.
Teams involved: Platform (internal)
Likely impact: Cutover-related incidents have a smaller team to respond. Increased Mean-Time-to-Mitigate.
Recommended action: Identify backup on-call cover for W6-7 from outside the immediate team (e.g. SRE rotation, or a senior eng pulled from another stream).

## ⚠ Resource (tech lead out + integration window)
Conflict: Payments tech lead is out W4. Platform ships the new auth service the same week. Payments will be making early integration decisions without their tech lead present.
Teams involved: Payments
Likely impact: Architecture decisions made without the right reviewer. Integration approach may need revisiting in W5.
Recommended action: Defer architecture commitments until W5; have Payments use W4 for environment setup and design-doc reading instead.

No-clash items (just FYI):
• Both teams have visibility into each other's vacation calendars — good.
• Cutover staffing is named and scheduled — good.
• Compliance freeze window is communicated in advance.

Questions to ask the two PMs:
1. Is the Payments compliance freeze actually no-merges (hard), or just no-production-deploys (softer)? Affects clash #2.
2. Could Platform ship the new auth service to a beta endpoint in W3 to give Payments integration runway, before the public release in W4?
3. Has either side already discussed the legacy-auth deprecation timing relative to the freeze? It feels like nobody noticed.
4. Is there a shared "single source of truth" calendar where these dates live, or are these tracked separately by team? Most clashes I see come from separate calendars.

// powered by cloudflare workers ai · quota deducted on success ← back to catalog