---
name: 'step-05-section-order'
description: 'Verify that page specification sections appear in standard WDS order with all required sections present'

# File References
nextStepFile: './step-06-object-registry.md'
workflowFile: '../workflow.md'
activityWorkflowFile: '../workflow-validate.md'
---

# Step 5: Validate Section Order & Structure

## STEP GOAL:

Verify that page specification sections appear in standard WDS order with all required sections present and no duplicate or redundant sections.

## 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 creative and thoughtful UX designer collaborating with the user
- ✅ 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 design expertise and systematic thinking, user brings product vision and domain knowledge
- ✅ Maintain creative and thoughtful tone throughout

### Step-Specific Rules:

- 🎯 Focus on section order, completeness, and absence of duplicates
- 🚫 FORBIDDEN to skip checking for duplicate or redundant sections
- 💬 Approach: Compare document structure against standard WDS order
- 📋 Consistent section order makes specifications predictable and enables automated tooling

## EXECUTION PROTOCOLS:

- 🎯 Scan document structure and compare against standard section order
- 💾 Update page specification if reordering is approved by user
- 📖 Reference standard WDS section order
- 🚫 FORBIDDEN to reorder sections without user approval

## CONTEXT BOUNDARIES:

- Available context: Page specification document structure
- Focus: Section order and completeness only
- Limits: Do not validate section content (that is covered by other steps)
- Dependencies: Page specification must exist

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

### 1. Check Section Order

Scan document structure and compare against standard section order:

1. Page Metadata
2. Navigation (H3 + Next Step + Sketch + Next Step + H1)
3. Page description paragraph
4. User Situation
5. Page Purpose
6. Page Sections
7. Object Registry
8. Reference Materials (optional)
9. Technical Notes (optional)
10. Development Checklist (optional)

### 2. Check for Duplicates and Redundancies

Identify:
- Sections that are out of order
- Missing required sections
- Duplicate sections
- Redundant or orphaned content

### 3. Generate Diagnostic Report

If required sections are missing, report as CRITICAL. If sections are out of order or duplicated, report as WARNING.

Generate diagnostic report showing current section order vs expected order, missing sections, and duplicates. Provide recommendation for correct ordering.

### 4. Resolve Issues

If issues found, present to user and ask if they want you to reorder or fix the section structure.

### 5. Record Validation Result

```yaml
section_order_validated:
  follows_standard_order: [true/false]
  all_required_sections_present: [true/false]
  no_duplicate_sections: [true/false]
  no_orphaned_content: [true/false]
  optional_sections_appropriate: [true/false]
  status: [pass/warning/critical]
```

### 6. Present MENU OPTIONS

Display: "**Select an Option:** [C] Continue to Validate Object Registry | [M] Return to Activity Menu"

#### Menu Handling Logic:

- IF C: Load, read entire file, then execute {nextStepFile}
- IF M: Return to {workflowFile} or {activityWorkflowFile}
- IF Any other comments or queries: help user respond then [Redisplay Menu Options](#6-present-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 the user selects an option from the menu and the section order validation is complete will you proceed to the next step or return as directed.

---

## 🚨 SYSTEM SUCCESS/FAILURE METRICS

### ✅ SUCCESS:

- Document structure scanned and compared against standard order
- All required sections checked for presence
- Duplicate and redundant sections identified
- Diagnostic report generated with current vs expected order
- Issues resolved with user approval
- Validation result recorded

### ❌ SYSTEM FAILURE:

- Not comparing against standard WDS section order
- Skipping duplicate detection
- Not checking for orphaned content
- Auto-reordering sections without user approval
- Proceeding without recording validation result

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