# AI Documentation Prompt: Feature Test Scenario Guide

**Role:** You are an expert **Technical Writer** and **QA Automation Architect**. Your goal is to create a "Feature Test Scenario Guide" based on the technical changes you just implemented in the workspace.

**Instructions:** Analyze the **code diff** and **workspace context** to generate a professional document following this structure:

---

### 1. Title
`# Test Scenario Guide: [Feature Name]`

### 2. Scenario Introduction
A brief overview of the **business or financial logic** behind this feature. Explain the "why" and "how" it fits into the system.

### 3. Technical Schema Changes (Detailed) 🔍
Analyze the changes in **FormRequest validation rules** and **API Responses**. List them clearly:

* **Endpoint:** `[Method] /endpoint_path`
* **Validation Changes:** * *Example:* Field `name` changed from `nullable` to `required`.
    * *Example:* Added `regex` validation or `max:255` constraint.
* **Response Changes:** * *Example:* Added `created_at` to the JSON response.
    * *Example:* Changed `user_id` type from `integer` to `uuid`.

### 4. Why the Update? (Change Log) 🔄
Compare the **"Previous Behavior"** vs. the **"New Behavior"**. Highlight benefits such as:
* Data integrity.
* Performance optimization.
* Improved security.

### 5. API Endpoints Table 📊
| Process | Endpoint | Method | Description |
| :--- | :--- | :--- | :--- |
| [Process Name] | `/api/v1/...` | `POST/GET` | Brief description of the action |

### 6. Test Cases 🧪
Define the following scenarios:

* **[Case 1] The Happy Path:** The standard successful workflow where all inputs are valid.
* **[Case 2] Backward Compatibility:** Ensuring that these changes do not break existing integrations or legacy data.
* **[Case 3] Edge Cases & Constraints:** * Testing **validation failures** (e.g., sending empty required fields).
    * Unauthorized access attempts.
    * Boundary values (e.g., minimum/maximum allowed amounts).

---

**Style Guidelines:**
* Use **professional technical English**.
* **Bold** key terms for high scannability.
* Use **Emojis** to distinguish sections.
* Always use **Markdown Tables** for endpoints.

**The information to process is:**
Analyze your current **workspace context** and the **latest code changes** you have performed (including FormRequests, Resources, Controllers, and Routes).