change-advisory-circle-manager

Coordinate cross-domain SOP changes through the Change Advisory Circle.

3|Updated Mar 29, 2026

Search Tags:#workflow #compliance #governance #cross-domain #auditable #change-advisory-circle #sop-governance

Ready to run

npx skills add https://github.com/SteveGJones/jack-tar-deckhand --skill change-advisory-circle-manager

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: change-advisory-circle-manager
Source: https://github.com/SteveGJones/jack-tar-deckhand/tree/main/.claude/skills/change-advisory-circle-manager
Command: npx skills add https://github.com/SteveGJones/jack-tar-deckhand --skill change-advisory-circle-manager

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Change Advisory Circle (CAC) governs cross-domain SOP changes to protect provider autonomy, respect consumer dependency, and maintain audit trails across SOP ownership and MCP servers.

Core Features & Use Cases

Defines CAC charter, composition, and decision-making rules for cross-domain SOP changes
Identifies cross-domain SOP clusters and establishes structured change requests, impact analyses, and testing requirements
Implements a formal change request workflow from submission to deployment, including impact analysis, CAC voting, and Nest testing plans
Provides emergency protocols, incident response, and post-incident retrospectives to protect operations
Delivers standardized governance artifacts: charters, meeting templates, dashboards, and onboarding materials

Quick Start

Identify cross-domain SOP clusters and initiate a CAC workflow to propose, review, and implement governance changes.

Frequently Asked Questions about change-advisory-circle-manager

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

FAQPage Schema

What is a Change Advisory Circle for cross-domain SOP governance?▼

A Change Advisory Circle (CAC) is a governance body that manages cross-domain SOP changes to protect provider autonomy, respect consumer dependencies, and maintain auditable trails across SOP ownership and MCP servers.

How do I manage cross-domain SOP ownership disputes?▼

Manage cross-domain SOP ownership disputes by applying CAC governance rules, which structure decision-making, voting, and impact analysis to resolve conflicts while maintaining formal audit trails.

How do I initiate a formal change request workflow for SOP modifications?▼

Initiate a SOP change request workflow by identifying cross-domain SOP clusters, submitting a proposal, conducting impact analysis, executing CAC voting, and deploying changes using standardized templates.

What governance artifacts are needed to audit cross-domain SOP changes?▼

Auditing cross-domain SOP changes requires standardized governance artifacts including the CAC charter, meeting templates, onboarding materials, dashboards, and formal decision logs.

Can I implement emergency protocols for cross-domain SOP modifications?▼

Yes, cross-domain SOP modifications include emergency protocols that define incident response procedures and post-incident retrospectives to protect operations during urgent MCP-server or SOP changes.

When do I need formal governance for MCP-server modifications?▼

You need formal CAC governance for MCP-server modifications when changes cross multiple domains, requiring structured impact analysis, voting, and testing to prevent breaking consumer dependencies.