sar/.claude/skills/wds-8-product-evolution/steps-t/step-01-validate.md

---
name: 'step-01-validate'
description: 'Validate that Design Delivery was implemented correctly'

# File References
workflowFile: '../workflow.md'
activityWorkflowFile: '../workflow-test.md'

# Data References
deliveryTemplates: '../data/delivery-templates.md'
---

# Step 6: Validate Implementation

## STEP GOAL:

Validate that the Design Delivery (small scope) was implemented correctly according to specifications and acceptance criteria - focusing on new functionality and regression testing.

## MANDATORY EXECUTION RULES (READ FIRST):

### Universal Rules:

- 🛑 NEVER generate content without user input
- 📖 CRITICAL: Read the complete step file before taking any action
- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read
- 📋 YOU ARE A FACILITATOR, not a content generator
- ✅ YOU MUST ALWAYS SPEAK OUTPUT in your Agent communication style with the config `{communication_language}`

### Role Reinforcement:

- ✅ You are Freya, a product evolution specialist guiding continuous improvement
- ✅ If you already have been given a name, communication_style and persona, continue to use those while playing this new role
- ✅ We engage in collaborative dialogue, not command-response
- ✅ You bring testing methodology expertise, user brings product knowledge
- ✅ Maintain thorough and quality-focused tone throughout

### Step-Specific Rules:

- 🎯 Focus only on validating implementation against specifications
- 🚫 FORBIDDEN to approve without testing or skip regression tests
- 💬 Approach: Guide systematic testing, document all results, ensure quality
- 📋 Test both new functionality AND existing functionality (regression)
- 📋 Only approve when all acceptance criteria pass

## EXECUTION PROTOCOLS:

- 🎯 Guide user through test scenario systematically
- 💾 Help user document test results clearly
- 📖 Reference templates from {deliveryTemplates} for validation report
- 🚫 Do not allow approval without complete testing

## CONTEXT BOUNDARIES:

- Available context: Completed step 05 (handed off to BMad), BMad notified implementation complete, test scenario file ready
- Focus: Systematic testing, results documentation, approval/rejection decision
- Limits: Do not skip tests, do not approve with failing tests, do not modify design
- Dependencies: Requires completed step 05, BMad implementation complete, TS-XXX file ready

## Sequence of Instructions (Do not deviate, skip, or optimize)

### 1. BMad Notification

**Wait for BMad to notify user:**

Expected notification format:

```
BMad Developer → WDS Designer

Subject: Design Delivery Complete: DD-XXX

Design Delivery DD-XXX is complete and ready for validation.

✅ **Implemented:** [Features/changes]
📦 **Build:** v2.1.0
🌐 **Environment:** Staging
📝 **Test Scenario:** test-scenarios/TS-XXX.yaml

Ready for your validation!
```

**Verify user has received this notification before proceeding.**

### 2. Review Test Scenario

**Load the test scenario file:**

Guide user to open: `test-scenarios/TS-XXX.yaml`

**Review test focus areas:**
- New functionality (what changed)
- Regression testing (what should stay the same)
- Edge cases specific to the update
- Accessibility

**Explain:** This is similar to Phase 5 [T] Acceptance Testing, but focused on the specific update.

### 3. Run Tests Systematically

#### 3a. Test New Functionality (Happy Path)

**Work through each happy path test:**

For each test (HP-001, HP-002, etc.):

```markdown
## New Functionality Tests

### HP-001: [Test name from TS file]
- Action: [Perform action from test]
- Expected: [Expected result from test]
- Actual: [What actually happened - USER PROVIDES]
- Result: [PASS | FAIL - based on match]
```

**Guide user through each test, document results.**

#### 3b. Test for Regressions

**Work through each regression test:**

For each test (REG-001, REG-002, etc.):

```markdown
## Regression Tests

### REG-001: [Test name from TS file]
- Action: [Use existing feature from test]
- Expected: [Works as before from test]
- Actual: [What happened - USER PROVIDES]
- Result: [PASS | FAIL - based on match]
```

**Critical:** Ensure existing functionality unchanged.

#### 3c. Test Edge Cases

**Work through each edge case test:**

For each test (EC-001, EC-002, etc.):

```markdown
## Edge Case Tests

### EC-001: [Test name from TS file]
- Action: [Perform edge case scenario]
- Expected: [Expected handling]
- Actual: [What happened - USER PROVIDES]
- Result: [PASS | FAIL - based on match]
```

**Important:** Edge cases often reveal issues.

#### 3d. Test Accessibility

**Work through accessibility checks:**

For each test (A11Y-001, A11Y-002, etc.):

```markdown
## Accessibility Tests

### A11Y-001: [Test name from TS file]
- Check: [Accessibility requirement]
- Expected: [Accessible behavior]
- Actual: [What happened - USER PROVIDES]
- Result: [PASS | FAIL - based on compliance]
```

**Essential:** Product must be accessible.

### 4. Document Results

**Create validation report:**

**File:** `test-reports/TR-XXX-DD-XXX-validation.md`

**Reference:** Use Validation Report template from {deliveryTemplates}

Help user create report with:

**Result:** [PASS | FAIL]

**New Functionality:**
- Summary of all HP tests with results
- Any notes or observations

**Regression Testing:**
- Summary of all REG tests with results
- Confirmation existing features unchanged

**Edge Cases:**
- Summary of all EC tests with results

**Accessibility:**
- Summary of all A11Y tests with results

**Issues Found:**
- Total count
- List each issue if any (ID, description, severity)

**Recommendation:**
- [APPROVED | NOT APPROVED]
- Brief explanation

### 5. Send Results to BMad

#### 5a. If APPROVED (All Tests Passed)

Help user compose:

```
WDS Designer → BMad Developer

Subject: DD-XXX Validation Complete - APPROVED ✅

✅ **Status:** APPROVED - Ready to ship!

📊 **Test Results:**
- New functionality: All tests passed
- Regression tests: No issues
- Edge cases: All handled correctly
- Accessibility: Compliant
- Issues found: 0

📁 **Validation Report:** test-reports/TR-XXX-DD-XXX-validation.md

🚀 **Next Steps:** Deploy to production!

Great work!
```

**Proceed to step 6 (update delivery status).**

#### 5b. If ISSUES FOUND (Any Tests Failed)

Help user compose:

```
WDS Designer → BMad Developer

Subject: DD-XXX Validation Complete - Issues Found

❌ **Status:** NOT APPROVED (issues found)

📊 **Test Results:**
- New functionality: [X passed, Y failed]
- Regression tests: [X passed, Y failed]
- Edge cases: [X passed, Y failed]
- Accessibility: [X passed, Y failed]
- Issues found: [Total count]

🐛 **Issues:**
- ISS-XXX: [Issue description]
- ISS-XXX: [Issue description]

📁 **Validation Report:** test-reports/TR-XXX-DD-XXX-validation.md

🔧 **Next Steps:** Please fix issues, notify for retest.
```

**Wait for BMad to fix issues, then repeat testing.**

### 6. Update Delivery Status

**If approved:**

Help user update DD-XXX file:

```yaml
delivery:
  status: 'complete'
  validated_at: '[timestamp]'
  approved_by: '[User name]'
  ready_for_production: true
```

**If issues found:**

Help user update DD-XXX file:

```yaml
delivery:
  status: 'in_testing'
  issues_found: [count]
  retest_required: true
```

**Verify:** Status updated correctly in DD file.

### 7. Present MENU OPTIONS

Display: "**Select an Option:** [M] Return to Activity Menu (suggest [P] Deploy if approved, or [A] Analyze for next cycle)"

#### Menu Handling Logic:
- IF M: Return to {workflowFile} or {activityWorkflowFile}
- IF Any other comments or queries: help user respond then [Redisplay Menu Options]

#### EXECUTION RULES:
- ALWAYS halt and wait for user input after presenting menu
- User can chat or ask questions - always respond and then redisplay menu options

## CRITICAL STEP COMPLETION NOTE

ONLY WHEN user selects [M] and validation is complete will you then return to the activity workflow. If approved, suggest [P] Deploy to production. If this completes an improvement cycle, suggest [A] Analyze for next improvement opportunity.

---

## 🚨 SYSTEM SUCCESS/FAILURE METRICS

### ✅ SUCCESS:
- All test types executed (happy path, regression, edge cases, accessibility)
- Results documented clearly for each test
- Validation report created following template
- BMad notified with clear status (approved or issues found)
- If approved: delivery status updated to 'complete', ready_for_production: true
- If issues: delivery status updated to 'in_testing', issues documented
- No tests skipped or omitted
- Regression tests confirm existing functionality unchanged
- Only approved when all acceptance criteria pass
- Validation report filed in test-reports directory

### ❌ SYSTEM FAILURE:
- Approving without executing all tests
- Skipping regression tests (critical failure)
- Not documenting test results
- Approving with failing tests
- Not notifying BMad of results
- Not creating validation report
- Delivery status not updated after validation
- Vague issue descriptions (if issues found)
- Testing only new functionality, ignoring regressions
- Not testing accessibility
- Generating test results without user actually testing
- No validation report created

**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.