Bmc Remedy Sr Designer

Convert SOPs and checklists into configuration-ready BMC Remedy Service Request and Work Order design documents.

Install
cmdop skills install agensi-bmc-remedy-sr-designer

BMC Remedy SR Designer is a skill that takes high-level process inputs — standard operating procedures, compliance checklists, and process artifacts — and transforms them into structured, configuration-ready design documents for BMC Remedy. The output targets Service Requests (SR), Work Orders (WO), or complex parent-child workflows that combine both.

The skill addresses a specific bottleneck: translating loosely defined business requirements into the rigid technical structures that BMC Remedy demands. That translation is typically manual and error-prone, requiring repeated clarification rounds between business analysts and BMC Administrators. This skill automates that step, producing a comprehensive Markdown document structured into ten distinct sections: Question Logic, Backend Tasks, Notification Templates, SLA Tables, Approval Flows, and Admin Configuration Notes.

The resulting document is intended as a handover artifact — a blueprint that a system administrator can pick up and implement directly without further interpretation. Every field mapping, conditional logic branch, and approval flow is documented to BMC platform conventions, reducing the back-and-forth that typically delays Remedy configuration projects.

This is a design-document generation skill with no tools exposed to agents. Its value is in the structured specification output, not in direct Remedy API interaction or live system configuration.

Use cases

  • Convert an IT onboarding SOP into a complete BMC Remedy Service Request design document
  • Generate parent-child Work Order workflow specifications from a compliance checklist
  • Produce Notification Template definitions for a Remedy SR without manual drafting
  • Document SLA tables and Approval Flows from process artifacts for handover to a BMC Admin
  • Translate a change management procedure into Remedy-ready Question Logic and Backend Task definitions

When to use it

  • When preparing a BMC Remedy SR or WO design document from existing SOPs or checklists
  • When a team needs a structured handover artifact for a BMC Administrator to implement
  • When designing complex parent-child Remedy workflows that require all sections documented consistently
  • When reducing manual effort and ambiguity in the requirements-to-Remedy translation step

When not to use it

  • When direct API interaction with a live BMC Remedy instance is required — this skill does not connect to Remedy
  • When the goal is to configure or deploy Remedy settings programmatically rather than produce a design document
  • When the source material is already in a Remedy-native format and no translation is needed
  • When the workflow target is an ITSM platform other than BMC Remedy