# Change Request: CR-XXX

> Created: YYYY-MM-DD
> Status: Pending
> Classification: [To be determined]
> Related Feature: FEATURE-XXX

## Request Details

**Requestor:** [Name/Role]
**Date Received:** YYYY-MM-DD
**Priority:** High | Medium | Low

## Description

[Detailed description of the change request]

## Business Justification

[Why this change is needed, business value]

## Impact Analysis

### Classification

**Type:** [Modification to FEATURE-XXX | New Feature]

**Reasoning:**
[Explain why this classification was chosen, referencing specific criteria]

### Comparison Matrix

| Aspect | CR Requirement | Existing Feature(s) |
|--------|---------------|---------------------|
| Users | [who uses this] | [current users] |
| Workflow | [new/changed flow] | [existing flow] |
| Data Model | [data changes] | [current data model] |
| UI Elements | [new screens] | [existing screens] |
| API Endpoints | [new APIs] | [existing APIs] |

### Affected Components

| Component | Impact Level | Details |
|-----------|--------------|---------|
| [Feature/Module] | High/Medium/Low | [What changes needed] |

### Dependencies

- [List any dependencies on other features or systems]

## Proposed Approach

[High-level approach to implementing this CR]

## Approval

- [ ] Classification approved by human
- [ ] Approach approved by human
- [ ] Ready for execution

## Execution

**Classification Result:** [modification | new_feature]

**Actions Taken:**
- [ ] CR document created in feature folder
- [ ] [If modification] Specification Version History updated with CR link
- [ ] [If new feature] Requirement details updated
- [ ] Next task type set: [task-type-feature-refinement | task-type-feature-breakdown]

## Links

- Feature Specification: [specification.md](./specification.md)
- Requirement Details: [requirement-details.md](../requirement-details.md)

---

## Change History

| Date | Change | By |
|------|--------|----|
| YYYY-MM-DD | CR created | [Agent/Human] |
