Write a change request with AI
Set out the reason for a proposed change, its impact, the rollout plan and the conditions for reversing it.
To write a change request with AI, give change-request the current process and the exact difference you want approved. The workflow covers impact, risk, implementation, rollback and communication. Removing one approval step from large orders, for example, can speed up sales while changing which checks Finance depends on.
Describe the observation that would make the team stop or reverse the change. A vague promise to monitor the outcome leaves the owner with little guidance if something goes wrong. A named decision role and a practical fallback make the request easier for the approver to assess.
What it does
- Explain the problem the change would address
- Identify affected teams and dependent processes
- Prepare an implementation sequence
- Define rollback conditions and ownership
- Draft the communication for affected people
Install and use
- Install the skill and supply the current process, proposal and known constraints. Optional IT service-management, tracker and chat actions need the Operations plugin and authorised connections.
- Ask “Draft the approval request for removing the second order check. Include the Finance impact and the condition for reverting the pilot.”
- Verify owners, timing and fallback before creating a connected ticket or notifying a team.
FAQ
Source
Made by Anthropic. Original skill: change-request, published on GitHub under the Apache-2.0 licence.
View on GitHub