change-request

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.

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.

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.

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.

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.

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.