initial commit
This commit is contained in:
139
_bmad/wds/workflows/4-ux-design/steps-v/step-02-navigation.md
Normal file
139
_bmad/wds/workflows/4-ux-design/steps-v/step-02-navigation.md
Normal file
@@ -0,0 +1,139 @@
|
||||
---
|
||||
name: 'step-02-navigation'
|
||||
description: 'Verify that page specification has proper navigation structure with headers, links, and embedded sketch'
|
||||
|
||||
# File References
|
||||
nextStepFile: './step-03-page-overview.md'
|
||||
workflowFile: '../workflow.md'
|
||||
activityWorkflowFile: '../workflow-validate.md'
|
||||
---
|
||||
|
||||
# Step 2: Validate Navigation Structure
|
||||
|
||||
## STEP GOAL:
|
||||
|
||||
Verify that page specification has proper navigation structure with H3 header, dual "Next Step" links, embedded sketch, and H1 page title.
|
||||
|
||||
## 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 validating navigation structure completeness and correctness
|
||||
- 🚫 FORBIDDEN to skip header matching or link validation
|
||||
- 💬 Approach: Check headers, links, sketch embedding, report findings, resolve with user
|
||||
- 📋 Consistent navigation enables automated tooling and cross-linking
|
||||
|
||||
## EXECUTION PROTOCOLS:
|
||||
|
||||
- 🎯 Validate navigation section at top of document
|
||||
- 💾 Update page specification if fixes are approved by user
|
||||
- 📖 Reference adjacent pages for link validation
|
||||
- 🚫 FORBIDDEN to skip link path validation
|
||||
|
||||
## CONTEXT BOUNDARIES:
|
||||
|
||||
- Available context: Page specification, adjacent page specifications
|
||||
- Focus: Navigation structure validation only
|
||||
- Limits: Do not validate page content or sections
|
||||
- Dependencies: Page specification must exist
|
||||
|
||||
## Sequence of Instructions (Do not deviate, skip, or optimize)
|
||||
|
||||
### 1. Check Navigation Elements
|
||||
|
||||
Check navigation section at top of document. Verify:
|
||||
- H3 header with page number and name
|
||||
- "Next Step" link before sketch (pointing to next page)
|
||||
- Embedded sketch image with proper path
|
||||
- "Next Step" link after sketch (same as first link)
|
||||
- H1 page title matching H3
|
||||
- Correct relative paths to adjacent pages
|
||||
- Page number consistency across all elements
|
||||
|
||||
### 2. Validate Sketch Embedding
|
||||
|
||||
Verify embedded sketch image exists and path is correct (typically `Sketches/[page-number]-[page-name]_[viewport].jpg`).
|
||||
|
||||
### 3. Generate Diagnostic Report
|
||||
|
||||
If navigation structure is missing or incomplete, report as CRITICAL. If links are broken or paths incorrect, report as WARNING.
|
||||
|
||||
Generate diagnostic report showing what's missing, incorrect paths, and provide example of correct navigation structure.
|
||||
|
||||
### 4. Resolve Issues
|
||||
|
||||
If issues found, present to user and ask if they want you to fix the navigation structure.
|
||||
|
||||
### 5. Record Validation Result
|
||||
|
||||
```yaml
|
||||
navigation_validated:
|
||||
h3_header_present: [true/false]
|
||||
h1_header_present: [true/false]
|
||||
headers_match: [true/false]
|
||||
page_numbers_consistent: [true/false]
|
||||
next_step_before_sketch: [true/false]
|
||||
next_step_after_sketch: [true/false]
|
||||
links_match: [true/false]
|
||||
sketch_embedded: [true/false]
|
||||
paths_valid: [true/false]
|
||||
status: [pass/warning/critical]
|
||||
```
|
||||
|
||||
### 6. Present MENU OPTIONS
|
||||
|
||||
Display: "**Select an Option:** [C] Continue to Validate Page Overview | [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 navigation validation is complete will you proceed to the next step or return as directed.
|
||||
|
||||
---
|
||||
|
||||
## 🚨 SYSTEM SUCCESS/FAILURE METRICS
|
||||
|
||||
### ✅ SUCCESS:
|
||||
|
||||
- All navigation elements checked (headers, links, sketch)
|
||||
- Header matching validated (H3 and H1 consistency)
|
||||
- Link paths validated against adjacent pages
|
||||
- Diagnostic report generated
|
||||
- Issues resolved with user approval
|
||||
- Validation result recorded
|
||||
|
||||
### ❌ SYSTEM FAILURE:
|
||||
|
||||
- Skipping header matching validation
|
||||
- Not checking link paths
|
||||
- Not validating sketch embedding
|
||||
- Auto-fixing issues 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.
|
||||
Reference in New Issue
Block a user