skills.rest
redacharf
redacharfCOMMUNITY
Explore all skills by this author →
GitHub

implementation-strategy

Decide compatibility strategies for runtime and API changes in openai-agents-js.

Updated Aug 23, 2026
Search Tags:#versioning#implementation#compatibility#migration#strategy#api-changes
One-click install
npx skills add https://github.com/redacharf/fin-punk --skill implementation-strategy-redacharf
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: implementation-strategy
Source: https://github.com/redacharf/fin-punk/tree/main/.agents/skills/implementation-strategy
Command: npx skills add https://github.com/redacharf/fin-punk --skill implementation-strategy-redacharf

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps engineering teams decide how to implement runtime and API changes while preserving compatibility, choosing between shims, migrations, or direct rewrites.

Core Features & Use Cases

  • Identify the surface being changed (released API, internal surface, or docs).
  • Determine compatibility boundaries against latest release tags, evaluate risk, and select a migration strategy.
  • Provide a clear, executable plan that minimizes disruption and ensures forward progress.

Quick Start

Assess the surface you are changing and determine the latest release boundary before editing code to decide the appropriate compatibility strategy.

Frequently Asked Questions about implementation-strategy

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is the best way to implement API changes without breaking compatibility?▼

To implement API changes safely, identify the changed surface, determine the latest release boundary, assess breaking-change risk, and select the simplest compatible approach like shims or migrations before editing code.

How do I choose between a shim, migration, or direct rewrite for runtime changes?▼

Choosing between a shim, migration, or rewrite requires assessing your breaking-change risk against the latest release boundary, then selecting the simplest compatible approach that minimizes disruption and ensures forward progress.

When do I need a migration strategy for altering exported APIs?▼

You need a migration strategy for altering exported APIs when a task changes runtime behavior, schemas, tests, or docs, requiring you to choose compatibility boundaries and rewrite timing before editing code.

How do I assess breaking-change risk before modifying runtime behavior?▼

Assess breaking-change risk by identifying the exact surface being changed—whether released API, internal surface, or docs—and evaluating it against the latest release tags to determine compatibility boundaries.

What are the limitations of direct rewrites for API schema changes?▼

Direct rewrites risk breaking compatibility if the changed surface crosses the latest release boundary, making shims or migrations safer alternatives to minimize disruption when altering exported APIs or schemas.

Related Skills

Explore More Software Engineering Skills→
openaiopenai
3.6k

implementation-strategy

Assess runtime and API compatibility boundaries before editing code.

Official
Advanced
D4nitrix13D4nitrix13

zod-4

Migrate Zod v3 schemas to Zod v4 APIs in TypeScript projects.

Community
Intermediate
heaptracetechnologyheaptracetechnology
13

contract-test

Automate API contract testing with schema validation and OpenAPI checks.

Community
Advanced
amanhsnamanhsn

Migration Architect

Generate phased migration plans with risk assessments and rollback strategies.

Community
Advanced