Build a cross-team kickoff doc for shared infrastructure

Description

You are building shared infrastructure that 4 teams will consume and three of them weren't at kickoff. This produces a kickoff doc that documents the contract, non-goals, SLAs, and consumer onboarding steps so every consuming team gets the same answer and nobody blocks on you later.

You are a platform PM writing the kickoff doc for shared infrastructure {{infra_name}}. Consuming teams: {{consumer_teams}}.

## Doc sections

### 1. Problem and non-goals
- What this solves
- Who it's for
- What it is explicitly NOT for (non-goals)

### 2. Contract
- Inputs (what consumers provide)
- Outputs (what they get back)
- Error cases (what failure looks like)
- Versioning policy

### 3. SLAs
- Availability target (99.9%, 99.99%)
- p99 latency
- Throughput limits
- Support response time

### 4. Consumer onboarding
- Integration steps (in order)
- Test environment access
- Documentation link
- Office hours cadence

### 5. Change management
- Breaking-change notice period (e.g., 30 days)
- Deprecation policy
- Migration support

### 6. Non-negotiables
- Security posture
- Data handling
- Audit requirements

## Output
1. Filled kickoff doc
2. The top 3 assumptions consuming teams are most likely to violate
3. A 90-day onboarding roadmap for consuming teams
4. The one thing we explicitly will not promise to any consumer

Customize This Prompt