change-request

Draft Change Requests from plain-language input into Project+ compliant documents.

Updated Apr 19, 2026

Search Tags:#governance #baseline #project-management #change-request #document-generation #ccb

Ready to run

npx skills add https://github.com/kenmulford/PMSkills --skill change-request-kenmulford

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: change-request
Source: https://github.com/kenmulford/PMSkills/tree/main/skills/change-request
Command: npx skills add https://github.com/kenmulford/PMSkills --skill change-request-kenmulford

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires python-docx, and includes scripts (resource) components.

What problem does it solve?

Change requests are high-stakes governance artifacts that must be auditable and free from fabrication. This skill provides a structured flow to draft, validate, and render a formal Change Request document from plain-language input, preserving user estimates and dispute-ready justification.

Core Features & Use Cases

Draft-first workflow: parse user input, fill a strict JSON schema, and generate a standardized CR document with clear citations to source phrases.
Baseline-safe: disposition governs baseline changes so no baseline shift occurs without explicit approval.
Use Case: create CRs for scope expansions, schedule shifts, or cost changes while tracking CCB membership and approvals.

Quick Start

Provide a brief project change description to generate a draft Change Request document.

Frequently Asked Questions about change-request

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I generate a formal change request document from plain text input?▼

To generate a change request, you provide a brief plain-language project change description, which the skill parses into a strict JSON schema and renders into a Project+ compliant document. It preserves your original estimates and cites source phrases.

Can I track baseline changes for scope, schedule, and cost impacts in a CR?▼

Yes, you can track baseline changes for scope, schedule, cost, quality, and resource impacts. The skill ties any baseline movement directly to the formal disposition, ensuring no baseline shift occurs without explicit CCB governance approval.

How do I ensure my change request is governance-ready and auditable?▼

You ensure a change request is governance-ready by using a draft-first workflow that enforces never-invent rules, tracks CCB membership and approvals, and produces dispute-ready justification. This prevents fabrication and creates high-integrity audit artifacts.

Does this change request generator work with python-docx for document rendering?▼

Yes, the skill uses python-docx as its dependency to render the standardized change request document. This allows you to output a properly formatted file directly from the structured plain-language input data.

What is the best way to document CCB approvals for project scope expansions?▼

The best way to document CCB approvals is to generate a formal change request that explicitly captures CCB membership and approval tracking. This ensures your scope expansion is tied to a formal disposition and remains fully auditable.

Will the change request skill invent estimates if I do not provide them?▼

No, the skill enforces strict never-invent rules and will not fabricate estimates. It preserves only the user-provided estimates and dispute-ready justification you supply in your plain-language input.