What problem does it solve? Change boards reject requests with missing answers, and teams lose track of what was filed when the same change process is copied across ServiceDesk Plus, Jira, and local files. This Skill keeps one canonical change-request template, enforces the ten mandatory questions with a validation gate, and maps every field correctly to whichever backend the team uses. ## Core Features & Use Cases - Single canonical template: One ServiceDesk Plus Change Management Request template reproduced identically across SDP, Jira, and local Markdown files, so wording never drifts between backends. - Enforced ten-question gate: The crew_change.py script validates answers in new mode (questions 1-9) and close mode (question 10, post-change validation), refusing empty or placeholder answers with a non-zero exit. - Backend field mapping: Maps Priority, Impact, Urgency, Requester, Implementor, scheduled window, and the ten Q&A pairs onto SDP fields, Jira issue fields, or a local .work/changes/<id>.md record. - Use Case: Before promoting a build to production, an engineer files a change request; the gate refuses submission until the rollback plan, affected users, and scheduled window are all answered, then writes the request to ServiceDesk Plus with metadata-resolved field values. ## Quick Start Ask the assistant to file a change request for your upcoming production deployment and answer the ten change-board questions it walks you through.
