Change Request Writer

Business operations skill, available on Zeplik

Change Request Writer is a ready-to-run business operations skill on Zeplik. Use when a system or process change needs formal approval -- 'write a change request for the DB migration', impact analysis, risk and rollback plan, CAB-ready change record, stakeholder comms for the rollout. Ask in plain language and Zeplik applies the skill's method for you inside the conversation, on whichever AI model you prefer. It returns a structured document you can keep and reuse: Document artifact -- structured written deliverable with headed sections and a TL;DR (see artifact-templates/document.md).

The Change Request Writer skill loads automatically when your request matches it, or you can invoke it directly by typing /change-request in any chat. It works with attachments, connectors, and any model that supports the task, so you get the same expert method every time without setting anything up.

What the Change Request Writer skill can do

Try these prompts on Zeplik

Pick a prompt to open it in the Zeplik app. If you are not signed in yet, your prompt is waiting for you the moment you do.

How the Change Request Writer skill works

/change-request

Create a structured change request with impact analysis, risk assessment, and rollback plan.

Usage

/change-request $ARGUMENTS

Change Management Framework

Apply the assess-plan-execute-sustain framework when building the request:

1. Assess

  • What is changing?
  • Who is affected?
  • How significant is the change? (Low / Medium / High)
  • What resistance should we expect?

2. Plan

  • Communication plan (who, what, when, how)
  • Training plan (what skills are needed, how to deliver)
  • Support plan (help desk, champions, FAQs)
  • Timeline with milestones

3. Execute

  • Announce and explain the "why"
  • Train and support
  • Monitor adoption
  • Address resistance

4. Sustain

  • Measure adoption and effectiveness
  • Reinforce new behaviors
  • Address lingering issues
  • Document lessons learned

Communication Principles

  • Explain the why before the what
  • Communicate early and often
  • Use multiple channels
  • Acknowledge what's being lost, not just what's being gained
  • Provide a clear path for questions and concerns

Output

## Change Request: [Title]
**Requester:** [Name] | **Date:** [Date] | **Priority:** [Critical/High/Medium/Low]
**Status:** Draft | Pending Approval | Approved | In Progress | Complete

### Description
[What is changing and why]

### Business Justification
[Why this change is needed — cost savings, compliance, efficiency, risk reduction]

### Impact Analysis
| Area | Impact | Details |
|------|--------|---------|
| Users | [High/Med/Low/None] | [Who is affected and how] |
| Systems | [High/Med/Low/None] | [What systems are affected] |
| Processes | [High/Med/Low/None] | [What workflows change] |
| Cost | [High/Med/Low/None] | [Budget impact] |

### Risk Assessment
| Risk | Likelihood | Impact | Mitigation |
|------|-----------|--------|------------|
| [Risk] | [H/M/L] | [H/M/L] | [How to mitigate] |

### Implementation Plan
| Step | Owner | Timeline | Dependencies |
|------|-------|----------|--------------|
| [Step] | [Person] | [Date] | [What it depends on] |

### Communication Plan
| Audience | Message | Channel | Timing |
|----------|---------|---------|--------|
| [Who] | [What to tell them] | [How] | [When] |

### Rollback Plan
[Step-by-step plan to reverse the change if needed]
- Trigger: [When to roll back]
- Steps: [How to roll back]
- Verification: [How to confirm rollback worked]

### Approvals Required
| Approver | Role | Status |
|----------|------|--------|
| [Name] | [Role] | Pending |

Working with the user's data

Zeplik chat has no live workplace connectors. When a step below expects system data, ask the user to paste the relevant export or upload the file, then proceed the same way.

If the user can share ITSM data (paste or upload):

  • Create the change request ticket automatically
  • Pull change advisory board schedule and approval workflows

If the user can share project tracker data (paste or upload):

  • Link to related implementation tasks and dependencies
  • Track change progress against milestones

If the user can share chat data (paste or upload):

  • Draft stakeholder notifications for the communication plan
  • Post change updates to the relevant team channels

Tips

  1. Be specific about impact — "Everyone" is not an impact assessment. "200 users in the billing team" is.
  2. Always have a rollback plan — Even if you're confident, plan for failure.
  3. Communicate early — Surprises create resistance. Previews create buy-in.

How to use the Change Request Writer skill

  1. Sign in to Zeplik

    Create a free Zeplik account or sign in. New accounts start with free credits, so you can try the Change Request Writer skill right away.

  2. Describe your business operations task

    Ask in plain language, or type /change-request to invoke the skill directly. Zeplik recognizes the Change Request Writer skill and applies its method.

  3. Review and refine the result

    Zeplik returns a structured document you can edit, download, and reuse. Ask follow-ups to refine it.

Source and credit

Author
Anthropic
License
Apache-2.0

Adapted from the open-source anthropics/knowledge-work-plugins project and tuned to run natively on Zeplik. View source on GitHub.

Frequently asked questions

What is the Change Request Writer skill?
Change Request Writer is a ready-to-run business operations skill on Zeplik. Use when a system or process change needs formal approval -- 'write a change request for the DB migration', impact analysis, risk and rollback plan, CAB-ready change record, stakeholder comms for the rollout. Ask in plain language and Zeplik applies the skill's method for you inside the conversation, on whichever AI model you prefer. It returns a structured document you can keep and reuse: Document artifact -- structured written deliverable with headed sections and a TL;DR (see artifact-templates/document.md).
How do I use Change Request Writer on Zeplik?
Sign in to Zeplik and ask in plain language, or type /change-request in any chat to invoke it directly. The skill applies its method and returns a result you can refine in the same conversation.
Which AI model does the Change Request Writer skill use?
Any model you choose. Zeplik works across every model in one chat, so the Change Request Writer skill runs on your preferred model for the task.
Where does the Change Request Writer skill come from?
The Change Request Writer skill is adapted from the open-source anthropics/knowledge-work-plugins project (Apache-2.0) and tuned to run natively on Zeplik. The original source is linked on this page.
How much does the Change Request Writer skill cost?
Using the skill is free to start. You only spend Zeplik credits when the assistant runs, and new accounts begin with free credits.

Related business operations skills

More on Zeplik

Try Change Request Writer on Zeplik

Every model, one chat. Bring the Change Request Writer skill into your next conversation and let the assistant do the work.

Browse all skills
Change Request Writer - Business operations skill for Zeplik AI | Zeplik Chat