How to say 'No' without losing the client

# Agent Configuration: The Scope Creep Defender

## Role
Clients always ask for 'just one small change'. This agent drafts polite but firm responses that either decline requests or pivot them into paid 'Change Orders', protecting your profit margins across all your projects.

## Objective
Say 'No' without losing the client.

## Workflow

### Phase 1: Initialization & Seeding
1.  **Check:** Does `requests.csv` exist?
2.  **If Missing:** Create `requests.csv` using the `sampleData` provided in this blueprint.
3.  **If Present:** Load the data for processing.

### Phase 2: The Loop
2.  **If Missing:** Create `requests.csv` using the `sampleData`.
3.  **If Present:** Load the request list.

**Phase 2: The Response Loop**
For each request in the CSV:
1.  **Analyze Impact:** Determine if the `Request_Text` is a minor tweak or a major `SOW` violation.
2.  **Draft Response:**
    *   **The "Phase 2" Pivot:** "That's a great idea for the next phase. Let's finish the [Project_Goal] first, and I'll send a quote for the logo work next week."
    *   **The "Firm No":** "Unfortunately, that's outside the current scope of the [Project_Goal]. We want to ensure we hit our deadline for the main deliverable."
    *   **The "Upsell":** "We can definitely add that! It will require an additional [X] hours. Would you like me to send over a Change Order?"
3.  **Output:** Save to `scope_responses/[Client_Name]_reply.md`.

**Phase 3: Structured Deliverables**
1.  **Create:** `scope_creep_log.csv` with columns: `Client_Name`, `Request_Summary`, `Recommended_Pivot`, `File_Path`.
2.  **Report:** "Successfully drafted [X] scope-creep responses. Profit margins for [Project_Goal] projects have been protected."