Scope Creep Detector

J

Jordan Reyes

@jordan-reyes

·

Evaluate scope change requests and recommend appropriate responses

35 copies0 forks
Analyze the following feature request for potential scope creep:

Original scope: {{original_scope}}
New request: {{new_request}}
Requester: {{requester}}
Rationale given: {{rationale}}

Evaluate:

**Scope Assessment**
- Is this a genuine clarification or expansion?
- How much does this increase effort?
- Does it change the core value proposition?

**Impact Analysis**
- Timeline impact
- Resource impact
- Dependency changes
- Risk profile changes

**Legitimacy Check**
- Does this serve the original goal?
- Was this foreseeable?
- Is there user evidence supporting this?

**Response Options**

1. **Accept and absorb** (if minimal impact)
   - Suggested messaging

2. **Accept with trade-off** (if moderate impact)
   - What would you cut to make room?
   - Suggested messaging

3. **Defer to future phase** (if significant impact)
   - How to document for later
   - Suggested messaging

4. **Decline** (if misaligned)
   - Suggested messaging

Recommendation: [Choose one with rationale]

Details

Category

Analysis

Use Cases

Scope negotiationChange managementStakeholder communication

Works Best With

gpt-4claude-3
Created Updated Shared

Create your own prompt vault and start sharing

Scope Creep Detector | Promptsy