governance-change-request

Capture and classify change requests for Providers.2.1.0 modules.

Updated Jan 6, 2026

Search Tags:#versioning #governance #impact-analysis #change-request #spec-update #approval-workflow

Ready to run

npx skills add https://github.com/cslsoftwares/ParamentersORM --skill governance-change-request

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: governance-change-request
Source: https://github.com/cslsoftwares/ParamentersORM/tree/main/.cursor/skills/governance-change-request_V1.0.0
Command: npx skills add https://github.com/cslsoftwares/ParamentersORM --skill governance-change-request

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Structured governance for change requests in existing Providers.2.1.0 modules, ensuring consistent intake, classification, impact assessment, approval, and traceability before implementation.

Core Features & Use Cases

Classify change types (correction, preventive, corrective, or evolution) and assess impact across scope, timeline, quality, and risk
Enforce breaking-change checks, obtain human approvals, and drive SPEC updates and documentation
Use case: when a modification is needed in Providers.2.1.0 modules; ensures formal review before coding

Quick Start

Submit a change request detailing the requester, description, and affected module to initiate the governance workflow.

Frequently Asked Questions about governance-change-request

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

FAQPage Schema

How do I manage change requests for existing modules with impact analysis?▼

Managing change requests with impact analysis involves capturing the requester, description, and affected component, then assessing scope, schedule, quality, and risk. This governance workflow enforces breaking-change checks and requires formal human approval before implementation.

What is a formal change request governance workflow?▼

A change request governance workflow standardizes the intake, classification, impact assessment, and approval of modifications. It ensures traceability from request initiation to deployment by enforcing SPEC updates and breaking-change checks for existing modules.

How do I classify change types during an approval workflow?▼

To classify change types during an approval workflow, categorize requests as correction, preventive, corrective, or evolution. This classification triggers the subsequent impact assessment across scope, timeline, quality, and risk dimensions.

Do I need human approval before implementing a spec update?▼

Yes, human approval is required before implementing a spec update. The governance workflow enforces formal review and breaking-change checks to ensure traceability and validate that all scope, schedule, and risk impacts are assessed prior to coding.

How do I start a change request for module modification?▼

To start a change request for module modification, submit the requester details, description, and the affected module information. This initiates the governance workflow, applying versioning controls before any formal review begins.

When should I not use an automated governance workflow for changes?▼

You should not use an automated governance workflow for changes that do not require formal classification or impact assessment. It is specifically designed for modifications needing scope, schedule, quality, and risk evaluation with enforced breaking-change checks.