What problem does it solve? Managing ServiceNow change requests requires navigating instance-specific state models, approval gates, conflict checks, and scheduling windows, which is error-prone when done manually through the UI or ad-hoc API calls. ## Core Features & Use Cases - Change Lifecycle Management: Create standard, normal, or emergency changes and drive them through legal state transitions using get_change_states as the authoritative source, never hardcoding state codes. - Scheduling & Conflict Detection: Check collisions against CI schedules and maintenance windows with check_change_conflicts, then book the earliest clear window via schedule_change_first_available. - Tasks & Risk Assessment: Create change tasks (CTASKs), track blockers to closure, and run the instance's risk/impact calculation before requesting approval. - Use Case: You need to deploy a server patch. Create a normal change, assess its risk, check for scheduling conflicts against the CI's maintenance window, book the first available slot, and progress it through assess, authorize, implement, and review states. ## Quick Start Create a normal ServiceNow change request for patching the web server, check for conflicts, and schedule it in the first available window.
