agentsclimarketplace
Sign in

Schema evolution governance

Skill planifest/planifest-framework/planifest-framework/external-skills/schema-evolution-governance

Schema evolution governance workflow for safe migration sequencing, compatibility control, and rollback readiness across dependent systems. Use when shared schemas change and end-to-end compatibility governance is required; do not use for isolated query micro-optimizations.From its SKILL.md

Install
npx -y skills add planifest/planifest-framework --skill schema-evolution-governance

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.0 KB, 327 tokens by cl100k_base, as published. Nobody here has run it

Schema Evolution Governance

Overview

Use this skill to evolve shared schemas without breaking producers, consumers, or historical data integrity.

Scope Boundaries

  • Use this skill when the task matches the trigger condition described in description.
  • Do not use this skill when the primary task falls outside this skill's domain.

Shared References

  • Compatibility window rules:
    • references/compatibility-window-rules.md

Templates And Assets

  • Schema change plan template:
    • assets/schema-change-plan-template.md
  • Schema compatibility checklist:
    • assets/schema-compatibility-checklist.md

Inputs To Gather

  • Current schema and migration history.
  • Producer/consumer dependency map.
  • Data volume, retention, and rollback constraints.
  • Release window and coordination limits.

Deliverables

  • Compatibility-aware schema change plan.
  • Phased migration sequence with checkpoints.
  • Rollback and data-recovery readiness criteria.

Workflow

  1. Define change impact in assets/schema-change-plan-template.md.
  2. Apply compatibility rules from references/compatibility-window-rules.md.
  3. Validate consumer migration sequence and cutover plan.
  4. Verify rollback/data integrity with assets/schema-compatibility-checklist.md.
  5. Publish execution ownership and residual risk log.

Quality Standard

  • Compatibility impact is explicit and testable.
  • Migration and rollback paths are both validated.
  • Consumer coordination is planned before destructive changes.

Failure Conditions

  • Stop when forward/backward compatibility is unverified.
  • Stop when rollback or data recovery path is missing.
  • Escalate when migration risk exceeds governance policy.

What ships with it: 1 file

11.3 KB alongside SKILL.md

Keep looking

Skills are one crate of 326,790. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.