Change Request Assessment

A structured prompt for using AI to evaluate an incoming change request — assessing scope impact, schedule impact, cost impact, and risk before presenting options to stakeholders.

Syntax

project-manager-ai

Evaluate this change request:

Requested change: [describe the change]
Current project status: [milestone, timeline, budget]

Assess:
1. Scope impact (what changes in scope)
2. Schedule impact (how many days/weeks added)
3. Resource impact (who is needed, for how long)
4. Risk introduced by the change
5. Options: Accept / Defer / Reject with reasoning

Example

project-manager-ai

Change request: Add two-factor authentication (2FA) to the login flow.

Scope impact: New API endpoints, UI changes to login and account settings, email/SMS service integration
Schedule impact: +2 to 3 weeks depending on SMS provider setup
Resource impact: 1 backend dev (2 weeks), 1 frontend dev (1 week), security review (3 days)
Risk: Delays beta launch; SMS costs not in current budget

Options:
- Accept: If security is a launch requirement — recommend adjusting timeline
- Defer to v1.1: If 2FA is not a blocker — ship basic auth now, add 2FA in next cycle
- Reject: Not recommended — 2FA is a common user expectation