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>
66 lines
1.2 KiB
Markdown
66 lines
1.2 KiB
Markdown
---
|
|
name: 'step-01-assess'
|
|
description: 'Load an existing output for editing'
|
|
nextStepFile: './step-02-apply-edit.md'
|
|
---
|
|
|
|
# Step 1: Assess Edit Target
|
|
|
|
## STEP GOAL:
|
|
|
|
Identify which output should be edited and load it.
|
|
|
|
## 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:
|
|
|
|
- 🎯 Ask the user which output file to edit
|
|
- 🚫 Do not edit until target is confirmed
|
|
|
|
## EXECUTION PROTOCOLS:
|
|
|
|
- 🎯 Follow the MANDATORY SEQUENCE exactly
|
|
|
|
## CONTEXT BOUNDARIES:
|
|
|
|
- Available context: existing outputs
|
|
- Focus: select edit target
|
|
- Limits: no edits yet
|
|
|
|
## MANDATORY SEQUENCE
|
|
|
|
**CRITICAL:** Follow this sequence exactly.
|
|
|
|
### 1. Identify Target
|
|
|
|
Ask the user to provide the output file path or select from known outputs.
|
|
|
|
### 2. Load Target
|
|
|
|
Read the provided output file in full.
|
|
|
|
### 3. Confirm
|
|
|
|
Confirm the target and proceed to edit.
|
|
|
|
Load next step: `{nextStepFile}`
|
|
|
|
## 🚨 SYSTEM SUCCESS/FAILURE METRICS:
|
|
|
|
### ✅ SUCCESS:
|
|
|
|
- Target identified and loaded
|
|
|
|
### ❌ SYSTEM FAILURE:
|
|
|
|
- Proceeding without a confirmed target
|