All skills
data-api-contract-changer
ProfessionalRuntime top levelAnalyze an API, schema, migration, or compatibility decision with analysis-agent, or implement its bounded contract change with task-agent. Do not select it when no data or public-contract surface is affected.
- Group
- Implementation owners
- Routing mode
- evidence-only
- Supported roles
- MainAnalysisTaskReview
- Source
- SKILL.md
Use when
Trigger signals that make this skill the right owner
- API contract change
- schema or migration change
Do not use when
Anti-triggers — as binding as the triggers above
- no data or public contract impact
- unrelated read-only analysis
Required inputs
What must be supplied before this skill can decide anything
- contract evidence
- compatibility requirements
Output contract
What this skill owes the next role
- contract transition
- consumer impact
- compatibility evidence
Escalation signals
When this skill must hand the decision back
- scope, authority, or material risk exceeds the selected task contract
Related expertise
12 Layer 3 candidates may be loaded behind this skill. A single task loads at most three, and only when the current evidence justifies them.
Targeted references
Each reference carries its own load condition. None of them enter context by default.
| Reference | Load when | Do not load when | Required by |
|---|---|---|---|
| checklist.mddecision-checklist | A bounded review needs concrete contract, pagination, migration, rollback, deprecation, and observability coverage | Consumer proof, generated diff, or performance/rollback tradeoff is the core risk | AnalysisTask |
| evidence-patterns.mdevidence-pattern | Closure depends on consumer proof, generated artifact diff, migration/rollback evidence, deprecation/deletion, or stale contract validation | High-level routing is enough and evidence is not being closed | AnalysisTask |
| index.mdindex | competing data api contract changer references require dependency, conflict, or output-fragment selection | the data api contract changer root or a task-named reference already resolves selection | AnalysisTask |
| solution-optimality.mdtargeted | A schema, API, event, version, migration, list/expansion, filter, or compatibility design has a material consumer, data-growth, or recovery tradeoff | The change is demonstrably additive and bounded with no affected consumer, storage, query, migration, or coexistence choice | AnalysisTask |