schema-reorder-governance

Enforce triple-backup, written plan, and human approval for repository schema-reorder operations.

Updated Jan 6, 2026
One-click install
npx skills add https://github.com/cslsoftwares/ParamentersORM --skill schema-reorder-governance
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: schema-reorder-governance
Source: https://github.com/cslsoftwares/ParamentersORM/tree/main/.cursor/skills/schema-reorder-governance_V1.0.0
Command: npx skills add https://github.com/cslsoftwares/ParamentersORM --skill schema-reorder-governance

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Organize and enforce governance for repository schema-reorder operations by mandating triple-backed backups, a formal plan, and explicit human approval before any changes to protected areas.

Core Features & Use Cases

  • Enforces a plan-driven, multi-backup workflow for schema changes
  • Requires explicit human authorization and stores approvals for auditing
  • Applies to protected areas such as Documentation/, .cursor/skills/, .cursor/rules/, .cursor/agents/, .cursor/Templates/, .workspace/rules/

Quick Start

Create a plan, perform a backup, and obtain explicit human approval before applying any change to protected areas.

Frequently Asked Questions about schema-reorder-governance

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

FAQPage Schema
How do I enforce approval gates for schema changes in protected directories?

Schema reorder governance prevents unauthorized modifications by mandating triple-backups, a written plan in .workspace/plans, and explicit human approval posted in chat before any write operation touches protected areas.

What directories are covered by schema reorder governance rules?

Schema reorder governance rules apply to protected areas including Documentation/, .cursor/skills/, .cursor/rules/, .cursor/agents/, .cursor/Templates/, and .workspace/rules, ensuring pre-conditions are met before changes.

How do I create a compliant backup and plan before reorganizing repository schemas?

To create a compliant backup and plan before reorganizing repository schemas, document a formal plan in .workspace/plans and perform a triple-backup, satisfying gates G0, G1, and G2 prior to any writes.

Why do I need explicit human approval for schema reorganization tasks?

Explicit human approval for schema reorganization tasks is required to provide an auditable governance trail, ensuring modifications to protected areas are authorized and documented before execution.

What are the limitations of relying on manual reviews for protected area schema reorders?

Relying on manual reviews for protected area schema reorders lacks an enforced audit trail and automated gate validation, failing to guarantee triple-backups or explicit human authorization across protected directories.