AI Playbook
Change preparation
Prepare evidence, dependencies, validation steps, and rollback considerations for a proposed change.
Copy this prompt
Replace the bracketed values, then paste it into an AI client connected to Stackyapper.
Run the "Change preparation" playbook using Stackyapper.
Inputs
- change request: [Change ticket identifier or proposed change description]
- maintenance window: [Optional proposed maintenance window] (optional)
Objective
Prepare evidence, dependencies, validation steps, and rollback considerations for a proposed change.
Required evidence
- Service tickets
Use when available
- Ticket history
- Managed devices
- Device policies
- Identity configuration
- Asset inventory
- Documentation
Procedure
1. Resolve the objective, scope, approvals, affected parties, and timing.
2. Collect relevant history, device, policy, configuration, asset, and runbook context.
3. Produce a pre-change plan with risks, validation, rollback, and approval gaps; execute nothing.
Return
- Change scope
- Dependencies and affected parties
- Risk and approval gaps
- Validation plan
- Rollback considerations
Use only evidence available through the Stackyapper Apps and permissions connected to this AI client. If required evidence is unavailable, say what is missing before continuing. Do not guess or make changes in connected systems.Before you paste
Replace every bracketed value in the prompt. Delete an optional input line if it does not apply.
change request: Change ticket identifier or proposed change description. (required)maintenance window: Optional proposed maintenance window. (optional)
What Stackyapper will use
The exact tools depend on the Apps connected to your workspace and the current user's permissions.
- Service tickets (required)
- Ticket history (used when available)
- Managed devices (used when available)
- Device policies (used when available)
- Identity configuration (used when available)
- Asset inventory (used when available)
- Documentation (used when available)
What you'll get
- Change scope
- Dependencies and affected parties
- Risk and approval gaps
- Validation plan
- Rollback considerations
How it works
- Resolve the objective, scope, approvals, affected parties, and timing.
- Collect relevant history, device, policy, configuration, asset, and runbook context.
- Produce a pre-change plan with risks, validation, rollback, and approval gaps; execute nothing.