cross-team-rfc-draft

name	cross-team-rfc-draft
description	Use when a planned change crosses team, service, or product boundaries and needs an RFC, design-doc review, or dependency request before implementation. Triggers on: RFC, design doc, cross-team review, dependency request, shared-kernel change, deprecation proposal, vendor swap, 'I need sign-off from team X', 'this changes a public interface', 'I want to deprecate endpoint Y'. Do NOT use for: design-time brainstorming for a single team (use obra/superpowers brainstorming, then obra/superpowers writing-plans), or for a per-PR review packet (use code-ownership-impact). Complementary to code-ownership-impact, which is the per-PR packet; cross-team-rfc-draft is the long-form RFC that has to be reviewed and signed off by N other teams, each with their own calendar and release train.
metadata	{"short-description":"Cross-team RFC drafting with named approvers and migration windows"}

Cross-Team RFC Draft

Draft an RFC for a change that crosses team, service, or product boundaries. The output is a review-ready RFC skeleton with named approvers, per-consumer-team migration windows, and a release-train-aware review order.

Required Loading

Always load:

• prompts/rfc-skeleton.md — the 9-section RFC template; the per-consumer-team migration-window section.

When To Run

• Before any change that crosses a public interface (auth token format, event schema, public API contract).
• Before any deprecation proposal (an endpoint, a package, a feature flag).
• Before any shared-kernel extraction (a package, a service, a CI template).
• Before any vendor swap (Stripe → Adyen, Datadog → Honeycomb, etc.).
• When a team has been blocked by another team's calendar and needs a written proposal to push the conversation past chat threads.