team-api-design

# Team API Design Skill

## When to Use This Skill

Use this skill when:

- **Team Api Design tasks** - Working on define team interfaces, contracts, and communication boundaries
- **Planning or design** - Need guidance on Team Api Design approaches
- **Best practices** - Want to follow established patterns and standards

## Overview

Define clear team interfaces, contracts, and communication boundaries using Team API patterns.

## MANDATORY: Documentation-First Approach

Before designing team APIs:

1. **Invoke `docs-management` skill** for team interface patterns
2. **Verify Team API concepts** via MCP servers (perplexity)
3. **Base guidance on Team Topologies team API framework**

## What is a Team API?

```text
TEAM API: The explicit interface a team exposes to other teams

┌─────────────────────────────────────────────────────────────────┐
│                          TEAM API                               │
├─────────────────────────────────────────────────────────────────┤
│                                                                 │
│  ┌──────────────┐  ┌──────────────┐  ┌──────────────┐          │
│  │   Code &     │  │  Versioning  │  │  Service     │          │
│  │   Artifacts  │  │   & Releases │  │   Catalog    │          │
│  └──────────────┘  └──────────────┘  └──────────────┘          │
│                                                                 │
│  ┌──────────────┐  ┌──────────────┐  ┌──────────────┐          │
│  │   Wiki &     │  │  Practices   │  │   Ways of    │          │
│  │   Docs       │  │   & Runbooks │  │   Working    │          │
│  └──────────────┘  └──────────────┘  └──────────────┘          │
│                                                                 │
│  ┌──────────────┐  ┌──────────────┐  ┌──────────────┐          │
│  │   Chat &     │  │   Office     │  │   Support    │          │
│  │   Channels   │  │   Hours      │  │   Rotation   │          │
│  └──────────────┘  └──────────────┘  └──────────────┘          │