Saad Ibn-Ezzoubayr
4807376c49
Add PriorityAlertsPanel component to the dashboard, update DashboardController with alert logic, and apply misc UI fixes across sidebar, forms, and pages. Includes epic-1 retrospective and sprint status update. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
61 lines
1.1 KiB
Markdown
61 lines
1.1 KiB
Markdown
---
|
|
name: 'step-02-apply-edit'
|
|
description: 'Apply edits to the selected output'
|
|
---
|
|
|
|
# Step 2: Apply Edits
|
|
|
|
## STEP GOAL:
|
|
|
|
Apply the requested edits to the selected output and confirm changes.
|
|
|
|
## MANDATORY EXECUTION RULES (READ FIRST):
|
|
|
|
### Universal Rules:
|
|
|
|
- 📖 Read the complete step file before taking any action
|
|
- ✅ Speak in `{communication_language}`
|
|
|
|
### Role Reinforcement:
|
|
|
|
- ✅ You are the Master Test Architect
|
|
|
|
### Step-Specific Rules:
|
|
|
|
- 🎯 Only apply edits explicitly requested by the user
|
|
|
|
## EXECUTION PROTOCOLS:
|
|
|
|
- 🎯 Follow the MANDATORY SEQUENCE exactly
|
|
|
|
## CONTEXT BOUNDARIES:
|
|
|
|
- Available context: selected output and user changes
|
|
- Focus: apply edits only
|
|
|
|
## MANDATORY SEQUENCE
|
|
|
|
**CRITICAL:** Follow this sequence exactly.
|
|
|
|
### 1. Confirm Requested Changes
|
|
|
|
Restate what will be changed and confirm.
|
|
|
|
### 2. Apply Changes
|
|
|
|
Update the output file accordingly.
|
|
|
|
### 3. Report
|
|
|
|
Summarize the edits applied.
|
|
|
|
## 🚨 SYSTEM SUCCESS/FAILURE METRICS:
|
|
|
|
### ✅ SUCCESS:
|
|
|
|
- Changes applied and confirmed
|
|
|
|
### ❌ SYSTEM FAILURE:
|
|
|
|
- Unconfirmed edits or missing update
|