원클릭으로 Manus에서 모든 스킬 실행

change-request-log

스타16

포크2

업데이트2026년 4월 30일 11:03

Extracts every IT change request from email — system upgrades, configuration changes, infrastructure modifications, deployment requests, and policy updates — tracking approval status, implementation status, and any changes that went ahead without proper approval. Use when an IT manager wants a change management log derived from email. Triggers on "change requests", "IT changes", "what system changes are pending", "change management log", "infrastructure changes", "deployment requests".

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

igptai

igptai/skills

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

Change Request Log

Prerequisites

This skill needs the iGPT MCP at https://mcp.igpt.ai/.

If the MCP tools aren't available or return an auth error, tell the user to install the iGPT plugin (/plugin marketplace add igptai/skills) or add https://mcp.igpt.ai/ as a connector, then complete OAuth and say "ready". Retry once after they confirm. Never invent tokens or OAuth URLs. For deeper troubleshooting: https://raw.githubusercontent.com/igptai/skills/main/shared/mcp-guard.md

What This Skill Does

Scans all IT email threads for change requests — system upgrades, configuration changes, infrastructure modifications, deployment approvals, and policy updates — and tracks each through the approval and implementation lifecycle, flagging any that bypassed the approval process or remain in limbo.

Workflow

Before calling any tool, collect these values from the user. Offer the defaults and let the user override them; do not invent values they did not give.
- [time_range] — what window of email to scan. The user may give this in any form ("last 60 days", "the last 2 months", "May 2024", "since the freeze ended"). Default: the last 60 days. Keep the user's natural phrasing for use in the ask input; convert to ISO dates separately for the search call.
- [system_scope] — either "all" (default) or a specific system to focus on.
- [system_clause] — derived. When [system_scope] is not "all", set to " for [system_scope]". When [system_scope] is "all", set to empty string.
Call search with:
- query: change request upgrade deploy configuration modify infrastructure approval CAB release rollout update patch (if [system_scope] is not "all", append the system name to the query)
- date_from: ISO start date derived from [time_range]
- date_to: ISO end date derived from [time_range] (or today if open-ended)
Call ask with:
- input: Review all IT email threads from [time_range][system_clause]. Identify every change request — system upgrades, configuration changes, infrastructure modifications, deployment requests, policy updates, and any other formal or informal IT change. For each change note: what was requested, who requested it, what system it affects, when it was requested, whether approval was obtained, whether the change has been implemented, and whether any change appears to have been made without following the proper approval process.
- output_format: { "strict": true, "schema": { "type": "object", "description": "IT change request log extracted from email threads", "additionalProperties": false, "properties": { "as_of": { "type": "string", "description": "ISO8601 date when this log was generated" }, "change_requests": { "type": "array", "description": "List of every IT change request found in email", "items": { "type": "object", "description": "A single IT change request with approval and implementation tracking", "additionalProperties": false, "properties": { "change_title": { "type": "string", "description": "Brief title describing the change" }, "change_type": { "type": "string", "description": "Category of IT change", "enum": [ "system_upgrade", "configuration_change", "infrastructure_modification", "deployment", "security_patch", "policy_update", "integration_change", "access_policy_change", "hardware_change", "other" ] }, "system_affected": { "type": "string", "description": "The system or infrastructure component this change affects" }, "requested_by": { "type": "string", "description": "Name or role of the person requesting this change" }, "requested_on": { "type": "string", "description": "ISO8601 date the change was requested" }, "risk_level": { "type": "string", "description": "Risk level of this change to system stability or security", "enum": ["high", "medium", "low", "unknown"] }, "approval_status": { "type": "string", "description": "Whether this change has been formally approved", "enum": [ "approved", "pending_approval", "denied", "implemented_without_approval", "unknown" ] }, "approved_by": { "type": "string", "description": "Name or role of the approver, empty string if not yet approved" }, "implementation_status": { "type": "string", "description": "Current implementation status of this change", "enum": [ "not_started", "scheduled", "in_progress", "implemented", "rolled_back", "on_hold", "unknown" ] }, "scheduled_date": { "type": "string", "description": "ISO8601 date the change is scheduled for, empty string if not scheduled" }, "bypass_flag": { "type": "boolean", "description": "Whether this change appears to have been implemented without proper approval" }, "notes": { "type": "string", "description": "Any additional context about this change from email, empty string if none" } }, "required": [ "change_title", "change_type", "system_affected", "requested_by", "requested_on", "risk_level", "approval_status", "approved_by", "implementation_status", "scheduled_date", "bypass_flag", "notes" ] } }, "pending_approval_count": { "type": "number", "description": "Number of change requests awaiting approval" }, "bypass_count": { "type": "number", "description": "Number of changes that appear to have been implemented without proper approval" }, "high_risk_pending_count": { "type": "number", "description": "Number of high-risk changes still awaiting approval or implementation" }, "summary": { "type": "string", "description": "One or two sentence summary of the change request backlog and any compliance concerns" } }, "required": [ "as_of", "change_requests", "pending_approval_count", "bypass_count", "high_risk_pending_count", "summary" ] } }
Present bypass-flagged changes and high-risk pending approvals first. Lead with bypass count and high_risk_pending count. Flag any unapproved high-risk changes as requiring immediate attention.
Ask: "Would you like me to draft an approval request or change communication for any of these items?"

이 저장소의 다른 Skills

같은 저장소

client-deliverable-tracker

igptai/skills

Tracks every deliverable committed to across active consulting engagements — what has been delivered, what is outstanding, what is overdue, and what feedback is still open. Use when a consultant or agency wants a full view of all client deliverable commitments without manually reviewing every thread. Triggers on "client deliverables", "what have I promised to deliver", "outstanding deliverables", "what is due to clients", "deliverable tracker", "what am I behind on".

2026-04-3016

client-feedback-collector

igptai/skills

Collects and structures all client feedback received across consulting engagements — formal feedback, informal reactions, satisfaction signals, and criticism — so the consultant has a consolidated view of how each client perceives the work. Use when a consultant wants to understand their client satisfaction landscape. Triggers on "client feedback", "what are clients saying about the work", "satisfaction signals", "collect feedback", "how happy are my clients", "client reactions".

2026-04-3016

proposal-follow-up-tracker

igptai/skills

Tracks every outstanding proposal sent to prospective clients — where each stands, how long it has been outstanding, whether feedback has been received, and which proposals have gone quiet. Use when a consultant wants a full view of their proposal pipeline and knows exactly who to follow up with. Triggers on "proposal follow-up", "outstanding proposals", "proposals waiting for a response", "proposal pipeline", "which proposals are pending", "proposal tracker".

2026-04-3016

reference-request-miner

igptai/skills

Finds every request for references, testimonials, case studies, and introductions buried in prospecting and client email threads — requests made by prospects, offers made by happy clients, and opportunities to ask for a reference that have not yet been actioned. Use when a consultant wants to build their reference network or respond to reference requests. Triggers on "reference requests", "who has offered to be a reference", "testimonial requests", "case study opportunities", "intro requests", "who can I use as a reference".

2026-04-3016

retainer-usage-tracker

igptai/skills

Tracks retainer hour and budget usage across active consulting retainer clients — how much has been used, what is remaining, whether any client is burning through their retainer unusually fast, and whether renewal conversations are needed. Use when a consultant wants to manage retainer utilization proactively. Triggers on "retainer usage", "how many hours have I used", "retainer balance", "retainer burn rate", "retainer renewal", "retainer tracker".

2026-04-3016

scope-creep-detector

igptai/skills

Detects scope creep signals across active consulting engagements — requests that go beyond the agreed statement of work, informal additions accepted without change orders, and patterns of expanding client expectations. Use when a consultant wants to identify where they are working outside scope and need to have a change order conversation. Triggers on "scope creep", "out of scope requests", "working outside the SOW", "scope expansion", "change order needed", "what's outside the original scope".

2026-04-3016

name	change-request-log
description	Extracts every IT change request from email — system upgrades, configuration changes, infrastructure modifications, deployment requests, and policy updates — tracking approval status, implementation status, and any changes that went ahead without proper approval. Use when an IT manager wants a change management log derived from email. Triggers on "change requests", "IT changes", "what system changes are pending", "change management log", "infrastructure changes", "deployment requests".
metadata	{"version":"1.0.0"}