Help us improve
Share bugs, ideas, or general feedback.
From chelsea-piers-itops
Generate a complete IT change request in CP format. Covers risk assessment, rollback plan, testing steps, and approval contacts. Use when: planning any configuration change, before executing write-enabled skills, or when the change advisory board needs a formal request. Activates on "change request", "change management", "CR", "I want to change", "planning a change", "approval needed", or before any significant IT action.
npx claudepluginhub afoxnyc3/chelsea-piers-itops --plugin chelsea-piers-itopsHow this skill is triggered — by the user, by Claude, or both
Slash command
/chelsea-piers-itops:change-request <description of proposed change, system affected, and planned window><description of proposed change, system affected, and planned window>The summary Claude sees in its skill listing — used to decide when to auto-load this skill
> No connector required — this skill produces a structured output document.
Provides Playwright E2E testing patterns including Page Object Model, test organization, configuration, CI/CD integration, and flaky test strategies.
Share bugs, ideas, or general feedback.
No connector required — this skill produces a structured output document.
Generate a complete change request document for IT configuration changes at Chelsea Piers.
/change-request $ARGUMENTS
| Risk | Criteria | Cerberus council? |
|---|---|---|
| LOW | Single user, read-only, or reversible in <5 min | No |
| MEDIUM | <10 users affected, reversible, tested procedure | No |
| HIGH | Production system, >10 users, firewall/CA policy, or irreversible | Yes — required |
| EMERGENCY | P1 incident in progress, no change window available | Yes — abbreviated council |
See Cerberus wiki general/it-ops-risk-patterns for the full risk classification table.
## Change Request — [CR-YYYY-MM-DD-NNN]
**Date submitted:** [date]
**Submitted by:** [name / role]
**Status:** Pending Approval
---
### 1. Change Description
[Clear, specific description of what will change. Include: system name, component,
current state, and proposed new state.]
### 2. Business Justification
[Why this change is needed. Link to incident ticket, security finding, or business requirement.]
### 3. Systems Affected
- **Primary:** [system name]
- **Secondary / dependent:** [list any downstream dependencies]
- **Users affected:** [estimated count and scope]
### 4. Risk Assessment
**Risk level:** LOW / MEDIUM / HIGH
| Risk | Likelihood | Impact | Mitigation |
|------|-----------|--------|-----------|
| [Risk 1] | Low/Med/High | Low/Med/High | [Mitigation] |
| [Risk 2] | Low/Med/High | Low/Med/High | [Mitigation] |
**Cerberus council verdict:** [APPROVE / CONDITIONAL / BLOCK — include conditions]
### 5. Change Window
- **Planned date:** [YYYY-MM-DD]
- **Start time:** [HH:MM ET]
- **Duration:** [estimated]
- **Blackout check:** [confirm no conflicting events or maintenance]
### 6. Testing Steps
1. [Pre-change validation step]
2. [Change execution step]
3. [Post-change validation step]
**Success criteria:** [How will you confirm the change worked?]
### 7. Rollback Plan
**Rollback trigger:** [What would cause you to roll back?]
**Rollback steps:**
1. [Step 1 — must be specific and executable]
2. [Step 2]
**Rollback time estimate:** [minutes]
### 8. Approval
| Role | Name | Required for |
|------|------|-------------|
| SysAdmin | [name] | All changes |
| IT Manager | [name] | MEDIUM and above |
| Security Analyst | [name] | Firewall, CA, identity changes |
| Cerberus council | [verdict] | HIGH risk changes |
**Approved by:** _____________________ Date: ___________
### 9. Post-Change Review
- [ ] Change completed successfully
- [ ] Success criteria verified
- [ ] Change log entry added to Confluence
- [ ] Jira ticket updated and closed
If ~~ticketing (Jira) is connected:
If ~~knowledge base (Confluence) is connected: