Plan a non-breaking evolution path for an event schema (additive-only changes, version field, deprecation cadence) compatible with consumer freezes.
Takes a current event schema and a desired future schema, produces a step-by-step evolution plan that keeps existing consumers working through the transition. Each step is provably backwards-compatible; only the final step retires deprecated fields.
current_schema: Avro, JSON Schema, or Protobuf source for the current shape.target_schema: the desired final shape.consumer_inventory: a list of consumer service names with their last-deploy date.deprecation_window_days: time consumers have to migrate (default 90).deprecated: true in step 1, remove in the final step after the deprecation window.schema_version integer to the schema if not present; bump it in each step.step1_date + deprecation_window_days).schema-evolution-plan.md with one section per step.schema-evolution-plan.md containing the three steps, each with the resulting schema (fenced), a compatibility verdict, and a date. Plus an Annex listing per-consumer action items. Stdout prints any unresolved migrations (renames the heuristic flagged ambiguous).
For each step's schema, run the Avro / Protobuf compatibility check (schema-registry-cli or protoc --fatal_warnings) against the previous step; the check must pass. Replay a sample of producer messages from the current schema against step 1's reader; deserialization must succeed. If the consumer inventory is missing dates or older than 1 year, extend the deprecation window proportionally rather than retire silently.
change_notes input or refuse without one.Other publishers' experience with this skill. Self-rating is blocked.
Sign in and publish to the registry to leave a rating.
No ratings yet. Be the first.
Same domains or capabilities as amitte/event-schema-evolution-planner.
Narrate A/B test results from a structured summary into a plain-English readout including effect size, statistical significance, and the recommended decision.
Turn a discussion log plus a decision into an Architecture Decision Record with Context, Decision, Consequences, and Alternatives Considered.
Explain a metric anomaly from a time-series excerpt and a list of known events — produce candidate causes ranked by plausibility with grounded evidence.
Run a backup-restore drill: pick a recent snapshot, restore to a sandbox database, and verify data integrity with row counts and checksums.
Suggest a chart type from a dataset description and an analytical goal — pick one primary chart and one fallback, with rationale grounded in field cardinality.
Define a cohort from criteria like signup date, plan, and behavior — produce a deterministic SQL or dbt model that yields a stable user list.