Skip to content
Back to skills

Playbook Backend Engineering Api V2

ASecurity

Introduce breaking API improvements while every existing client keeps working.

  • 2 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 29, 2026
ai-agentsbashgitapidatabasebackend

Works with

  • cli
  • api

Security analysis

A100/100

Scanned September 29, 2026

npx -y skills add aniruddhaadak80/skills --skill playbook-backend-engineering-api-v2 --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Playbook Backend Engineering Api V2?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Playbook Backend Engineering Api V2
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/aniruddhaadak80-playbook-backend-engineering-api-v2/badge)](https://www.skillsdirectory.com/skills/aniruddhaadak80-playbook-backend-engineering-api-v2)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: playbook-backend-engineering-api-v2
description: "Introduce breaking API improvements while every existing client keeps working."
---
# Playbook: Ship an API v2 safely

> Introduce breaking API improvements while every existing client keeps working.

**Track:** 🗺️ Backend Engineering · **Domain:** Journey Playbooks · **Level:** journey · **~80 min**

**Who this is for:** Backend Engineers, API Developers, Platform Engineers, Full-Stack Developers

## When to Use This Skill

Introduce breaking API improvements while every existing client keeps working.
Use it whenever a matching task appears in conversation — the agent loads these instructions on demand.

## Journey Steps

1. Step 1 — Migrate API versions without breaking clients: start with "Ship vN+1 alongside vN behind the same gateway; no big-bang cutover"
2. Step 2 — Run zero-downtime schema migrations: start with "Expand: add nullable columns/tables first; deploy code writing both paths"
3. How it fits together: Expand-contract thinking applies to both schema AND endpoint surface. Parallel-run is the whole game.

### Referenced Skills

- `api-design-api-versioning-migration`
- `databases-zero-downtime-migrations`

## Commands

**Install all referenced skills**
```bash
npx skills add aniruddhaadak80/skills --skill api-design-api-versioning-migration && npx skills add aniruddhaadak80/skills --skill databases-zero-downtime-migrations
```

---

Part of [aniruddhaadak80/skills](https://github.com/aniruddhaadak80/skills) · Browse all at https://skills.sh/aniruddhaadak80/skills

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…