code-framework 1.0.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +110 -0
- package/_code/agents/atlas.agent.yaml +58 -0
- package/_code/agents/builder.agent.yaml +58 -0
- package/_code/agents/echo.agent.yaml +58 -0
- package/_code/agents/iris.agent.yaml +70 -0
- package/_code/agents/luna.agent.yaml +62 -0
- package/_code/agents/phoenix.agent.yaml +58 -0
- package/_code/agents/sage.agent.yaml +58 -0
- package/_code/agents/scout.agent.yaml +54 -0
- package/_code/templates/epic-template.md +81 -0
- package/_code/templates/sitemap-template.md +74 -0
- package/_code/templates/story-template.md +121 -0
- package/_code/templates/wireframe-prompt-template.md +153 -0
- package/_code/workflows/brief/steps/step-01-brainstorm.md +191 -0
- package/_code/workflows/brief/steps/step-02-requirements.md +230 -0
- package/_code/workflows/brief/steps/step-03-inspiration.md +285 -0
- package/_code/workflows/brief/steps/step-04-entities.md +359 -0
- package/_code/workflows/brief/steps/step-05-framework.md +455 -0
- package/_code/workflows/brief/steps/step-06-review.md +370 -0
- package/_code/workflows/brief/workflow.md +52 -0
- package/_code/workflows/docs/steps/step-01-validate.md +256 -0
- package/_code/workflows/docs/steps/step-02-epic.md +310 -0
- package/_code/workflows/docs/steps/step-03-story.md +338 -0
- package/_code/workflows/docs/steps/step-04-plan.md +348 -0
- package/_code/workflows/docs/workflow.md +127 -0
- package/_code/workflows/evolve/steps/step-01-version.md +297 -0
- package/_code/workflows/evolve/steps/step-02-scope.md +279 -0
- package/_code/workflows/evolve/steps/step-03-context.md +365 -0
- package/_code/workflows/evolve/steps/step-04-changelog.md +297 -0
- package/_code/workflows/evolve/workflow.md +103 -0
- package/_code/workflows/help.md +387 -0
- package/_code/workflows/implement/steps/step-01-select.md +214 -0
- package/_code/workflows/implement/steps/step-02-code.md +275 -0
- package/_code/workflows/implement/steps/step-03-test.md +327 -0
- package/_code/workflows/implement/steps/step-04-done.md +317 -0
- package/_code/workflows/implement/workflow.md +77 -0
- package/_code/workflows/outline/steps/step-01-analyze.md +344 -0
- package/_code/workflows/outline/steps/step-02-schema.md +369 -0
- package/_code/workflows/outline/steps/step-03-api.md +316 -0
- package/_code/workflows/outline/steps/step-04-stack.md +300 -0
- package/_code/workflows/outline/workflow.md +103 -0
- package/_code/workflows/party/workflow.md +69 -0
- package/_code/workflows/review/steps/step-01-checklist.md +354 -0
- package/_code/workflows/review/steps/step-02-qa.md +363 -0
- package/_code/workflows/review/workflow.md +138 -0
- package/_code/workflows/status.md +177 -0
- package/_code/workflows/ux/steps/step-01-sitemap.md +251 -0
- package/_code/workflows/ux/steps/step-02-wireframes.md +394 -0
- package/_code/workflows/ux/steps/step-03-flows.md +384 -0
- package/_code/workflows/ux/steps/step-04-validate.md +344 -0
- package/_code/workflows/ux/workflow.md +70 -0
- package/install.js +194 -0
- package/package.json +37 -0
- package/project-template/.claude/commands.yaml +356 -0
- package/project-template/.claude/settings.json +11 -0
- package/project-template/1-context/_active.yaml +15 -0
- package/project-template/1-context/v1.0.0/1-brainstorm/idea.md +40 -0
- package/project-template/1-context/v1.0.0/2-requirements/requirements.md +62 -0
- package/project-template/1-context/v1.0.0/3-inspiration/inspiration.md +64 -0
- package/project-template/1-context/v1.0.0/3-inspiration/moodboard/.gitkeep +5 -0
- package/project-template/1-context/v1.0.0/4-entities/entities.md +119 -0
- package/project-template/1-context/v1.0.0/5-framework/framework.md +89 -0
- package/project-template/2-outline/v1.0.0/.gitkeep +9 -0
- package/project-template/3-ux/v1.0.0/.gitkeep +9 -0
- package/project-template/3-ux/v1.0.0/wireframes/.gitkeep +7 -0
- package/project-template/4-documentation/epics/.gitkeep +10 -0
- package/project-template/4-documentation/stories/.gitkeep +15 -0
- package/project-template/5-evolution/changelog.md +58 -0
- package/project-template/research/.gitkeep +16 -0
|
@@ -0,0 +1,384 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: 'step-03-flows'
|
|
3
|
+
description: 'Document user flows and navigation paths through the application'
|
|
4
|
+
nextStepFile: './step-04-validate.md'
|
|
5
|
+
previousStepFile: './step-02-wireframes.md'
|
|
6
|
+
outputFile: '3-ux/{version}/user-flows.md'
|
|
7
|
+
---
|
|
8
|
+
|
|
9
|
+
# Step 3: User Flows
|
|
10
|
+
|
|
11
|
+
## MANDATORY EXECUTION RULES (READ FIRST)
|
|
12
|
+
|
|
13
|
+
- đ **NEVER** create flows without sitemap and requirements
|
|
14
|
+
- đ **CRITICAL**: Flows must connect actual sitemap pages
|
|
15
|
+
- đ¯ Focus on CRITICAL USER JOURNEYS first
|
|
16
|
+
- đŦ Include decision points and error paths
|
|
17
|
+
- âšī¸ **HALT** at menu and wait for user selection
|
|
18
|
+
- đĢ **FORBIDDEN** to create flows with pages not in sitemap
|
|
19
|
+
|
|
20
|
+
## YOUR IDENTITY
|
|
21
|
+
|
|
22
|
+
You are **LUNA**. In this step, you're mapping HOW users move through your application. Flows reveal gaps, friction points, and opportunities for improvement.
|
|
23
|
+
|
|
24
|
+
**Key Principle:** A user flow is a story. It has a beginning (goal), middle (steps), and end (success or failure).
|
|
25
|
+
|
|
26
|
+
## SEQUENCE OF INSTRUCTIONS
|
|
27
|
+
|
|
28
|
+
### 1. Load Prerequisites
|
|
29
|
+
|
|
30
|
+
**REQUIRED: Read these files:**
|
|
31
|
+
|
|
32
|
+
```
|
|
33
|
+
3-ux/{version}/sitemap.md
|
|
34
|
+
1-context/{version}/2-requirements/requirements.md
|
|
35
|
+
1-context/{version}/4-entities/entities.md
|
|
36
|
+
```
|
|
37
|
+
|
|
38
|
+
**Extract:**
|
|
39
|
+
- All pages and their routes
|
|
40
|
+
- User types and their permissions
|
|
41
|
+
- Key requirements that imply journeys
|
|
42
|
+
|
|
43
|
+
### 2. Identify Critical User Journeys
|
|
44
|
+
|
|
45
|
+
Based on requirements, identify the essential flows:
|
|
46
|
+
|
|
47
|
+
```
|
|
48
|
+
## Critical User Journeys
|
|
49
|
+
|
|
50
|
+
Based on your requirements, these are the essential user flows:
|
|
51
|
+
|
|
52
|
+
### Must Have Flows (P0)
|
|
53
|
+
1. **New User Registration Flow**
|
|
54
|
+
- Goal: Create account and get started
|
|
55
|
+
- Requirements: FR-001, FR-002
|
|
56
|
+
|
|
57
|
+
2. **Returning User Login Flow**
|
|
58
|
+
- Goal: Access their account
|
|
59
|
+
- Requirements: FR-003, FR-004
|
|
60
|
+
|
|
61
|
+
3. **[Core Feature] Flow**
|
|
62
|
+
- Goal: [Primary user goal]
|
|
63
|
+
- Requirements: FR-005, FR-006, FR-007
|
|
64
|
+
|
|
65
|
+
4. **[Another Core Feature] Flow**
|
|
66
|
+
- Goal: [Primary user goal]
|
|
67
|
+
- Requirements: FR-008, FR-009
|
|
68
|
+
|
|
69
|
+
### Should Have Flows (P1)
|
|
70
|
+
5. **Password Reset Flow**
|
|
71
|
+
- Goal: Recover access to account
|
|
72
|
+
- Requirements: FR-010
|
|
73
|
+
|
|
74
|
+
6. **Profile Update Flow**
|
|
75
|
+
- Goal: Modify account settings
|
|
76
|
+
- Requirements: FR-011
|
|
77
|
+
|
|
78
|
+
### Nice to Have Flows (P2)
|
|
79
|
+
7. **[Enhancement Feature] Flow**
|
|
80
|
+
- Goal: [Secondary user goal]
|
|
81
|
+
- Requirements: FR-020
|
|
82
|
+
|
|
83
|
+
Which flows should we document first?
|
|
84
|
+
[1-7] Select a number
|
|
85
|
+
[A] All flows in order
|
|
86
|
+
[P] P0 flows only for now
|
|
87
|
+
```
|
|
88
|
+
|
|
89
|
+
### 3. Document Each Flow
|
|
90
|
+
|
|
91
|
+
For each selected flow, create a detailed diagram:
|
|
92
|
+
|
|
93
|
+
```markdown
|
|
94
|
+
# User Flow: New User Registration
|
|
95
|
+
|
|
96
|
+
## Flow Metadata
|
|
97
|
+
|
|
98
|
+
| Field | Value |
|
|
99
|
+
|-------|-------|
|
|
100
|
+
| Flow ID | UF-001 |
|
|
101
|
+
| Name | New User Registration |
|
|
102
|
+
| Priority | P0 |
|
|
103
|
+
| User Type | Visitor â New User |
|
|
104
|
+
| Goal | Create account and access dashboard |
|
|
105
|
+
| Requirements | FR-001, FR-002, FR-003 |
|
|
106
|
+
|
|
107
|
+
## Flow Overview
|
|
108
|
+
|
|
109
|
+
**Trigger:** User clicks "Sign Up" on any page
|
|
110
|
+
**Success:** User lands on Dashboard with account created
|
|
111
|
+
**Failure:** User sees error and can retry
|
|
112
|
+
|
|
113
|
+
## Flow Diagram (Mermaid)
|
|
114
|
+
|
|
115
|
+
```mermaid
|
|
116
|
+
graph TD
|
|
117
|
+
A[Landing Page P001] --> B{Click Sign Up}
|
|
118
|
+
B --> C[Sign Up Page P002]
|
|
119
|
+
C --> D[Fill Form]
|
|
120
|
+
D --> E{Valid?}
|
|
121
|
+
E -->|No| F[Show Errors]
|
|
122
|
+
F --> D
|
|
123
|
+
E -->|Yes| G[Submit Form]
|
|
124
|
+
G --> H{Email Unique?}
|
|
125
|
+
H -->|No| I[Show "Email Exists" Error]
|
|
126
|
+
I --> D
|
|
127
|
+
H -->|Yes| J[Create Account]
|
|
128
|
+
J --> K[Send Verification Email]
|
|
129
|
+
K --> L[Verification Pending Page P003]
|
|
130
|
+
L --> M{User Clicks Email Link}
|
|
131
|
+
M -->|Yes| N[Email Verified]
|
|
132
|
+
N --> O[Dashboard P004]
|
|
133
|
+
M -->|No/Expired| P[Resend Option]
|
|
134
|
+
P --> K
|
|
135
|
+
```
|
|
136
|
+
|
|
137
|
+
## Step-by-Step Breakdown
|
|
138
|
+
|
|
139
|
+
### Step 1: Entry Point
|
|
140
|
+
- **Page:** P001 (Landing) or P003 (Login)
|
|
141
|
+
- **Action:** User clicks "Sign Up" button/link
|
|
142
|
+
- **Result:** Navigate to Sign Up page
|
|
143
|
+
|
|
144
|
+
### Step 2: Sign Up Form
|
|
145
|
+
- **Page:** P002 (Sign Up)
|
|
146
|
+
- **Action:** User enters email, password, name
|
|
147
|
+
- **Validation:**
|
|
148
|
+
- Email format valid
|
|
149
|
+
- Password meets requirements (8+ chars, etc.)
|
|
150
|
+
- Name not empty
|
|
151
|
+
- **Error States:**
|
|
152
|
+
- Invalid email â Inline error
|
|
153
|
+
- Weak password â Show requirements
|
|
154
|
+
- Empty fields â Highlight required
|
|
155
|
+
|
|
156
|
+
### Step 3: Form Submission
|
|
157
|
+
- **Action:** User clicks "Create Account"
|
|
158
|
+
- **Server Validation:**
|
|
159
|
+
- Check email not already registered
|
|
160
|
+
- **Error States:**
|
|
161
|
+
- Email exists â "An account with this email already exists. [Log in instead]"
|
|
162
|
+
- Server error â "Something went wrong. Please try again."
|
|
163
|
+
|
|
164
|
+
### Step 4: Email Verification
|
|
165
|
+
- **Page:** P003 (Verification Pending)
|
|
166
|
+
- **Display:** "Check your email to verify your account"
|
|
167
|
+
- **Actions Available:**
|
|
168
|
+
- Resend verification email
|
|
169
|
+
- Change email address
|
|
170
|
+
- Log out
|
|
171
|
+
|
|
172
|
+
### Step 5: Verify Email
|
|
173
|
+
- **Trigger:** User clicks link in email
|
|
174
|
+
- **Validation:** Token valid and not expired
|
|
175
|
+
- **Error States:**
|
|
176
|
+
- Expired token â "This link has expired. [Resend verification]"
|
|
177
|
+
- Invalid token â "Invalid link. [Resend verification]"
|
|
178
|
+
|
|
179
|
+
### Step 6: Success
|
|
180
|
+
- **Page:** P004 (Dashboard)
|
|
181
|
+
- **Result:** User is logged in with verified account
|
|
182
|
+
- **Optional:** Show onboarding tour
|
|
183
|
+
|
|
184
|
+
## Decision Points
|
|
185
|
+
|
|
186
|
+
| Decision | Options | Outcome |
|
|
187
|
+
|----------|---------|---------|
|
|
188
|
+
| Email exists? | Yes | Show error, link to login |
|
|
189
|
+
| Email exists? | No | Continue registration |
|
|
190
|
+
| Email verified? | Yes | Access dashboard |
|
|
191
|
+
| Email verified? | No | Show verification pending |
|
|
192
|
+
|
|
193
|
+
## Error Recovery Paths
|
|
194
|
+
|
|
195
|
+
| Error | Recovery Path |
|
|
196
|
+
|-------|---------------|
|
|
197
|
+
| Email already registered | Link to login page, password reset |
|
|
198
|
+
| Verification email lost | Resend verification option |
|
|
199
|
+
| Link expired | Auto-resend, manual resend button |
|
|
200
|
+
| Server error | Retry button, support contact |
|
|
201
|
+
|
|
202
|
+
## Success Metrics
|
|
203
|
+
|
|
204
|
+
- [ ] User can complete flow in < 2 minutes
|
|
205
|
+
- [ ] Error messages are actionable
|
|
206
|
+
- [ ] User can recover from all error states
|
|
207
|
+
- [ ] Mobile experience matches desktop
|
|
208
|
+
|
|
209
|
+
---
|
|
210
|
+
*Flow ID: UF-001*
|
|
211
|
+
*Last updated: {date}*
|
|
212
|
+
```
|
|
213
|
+
|
|
214
|
+
### 4. Create Flow Summary Document
|
|
215
|
+
|
|
216
|
+
After documenting flows, create a summary:
|
|
217
|
+
|
|
218
|
+
```markdown
|
|
219
|
+
# User Flows
|
|
220
|
+
|
|
221
|
+
## Overview
|
|
222
|
+
|
|
223
|
+
| Flow ID | Name | Priority | Pages Involved | Status |
|
|
224
|
+
|---------|------|----------|----------------|--------|
|
|
225
|
+
| UF-001 | Registration | P0 | P001, P002, P003, P004 | â
|
|
|
226
|
+
| UF-002 | Login | P0 | P003, P004 | â
|
|
|
227
|
+
| UF-003 | [Core Flow] | P0 | P005, P006, P007 | â
|
|
|
228
|
+
| UF-004 | Password Reset | P1 | P003, P008 | â
|
|
|
229
|
+
|
|
230
|
+
## Navigation Map
|
|
231
|
+
|
|
232
|
+
```mermaid
|
|
233
|
+
graph LR
|
|
234
|
+
Landing[P001 Landing] --> SignUp[P002 Sign Up]
|
|
235
|
+
Landing --> Login[P003 Login]
|
|
236
|
+
SignUp --> Dashboard[P004 Dashboard]
|
|
237
|
+
Login --> Dashboard
|
|
238
|
+
Dashboard --> Feature[P005 Feature List]
|
|
239
|
+
Feature --> Detail[P006 Feature Detail]
|
|
240
|
+
Detail --> Edit[P007 Feature Edit]
|
|
241
|
+
Dashboard --> Settings[P008 Settings]
|
|
242
|
+
```
|
|
243
|
+
|
|
244
|
+
## Critical Paths
|
|
245
|
+
|
|
246
|
+
### Happy Path: New User
|
|
247
|
+
Landing â Sign Up â Verify Email â Dashboard â [Core Feature]
|
|
248
|
+
|
|
249
|
+
### Happy Path: Returning User
|
|
250
|
+
Landing â Login â Dashboard â [Core Feature]
|
|
251
|
+
|
|
252
|
+
### Error Recovery
|
|
253
|
+
Any Error â Error Message â Retry/Alternative Path â Success
|
|
254
|
+
|
|
255
|
+
## Page Transition Matrix
|
|
256
|
+
|
|
257
|
+
| From/To | P001 | P002 | P003 | P004 | P005 |
|
|
258
|
+
|---------|------|------|------|------|------|
|
|
259
|
+
| P001 | - | â | â | - | - |
|
|
260
|
+
| P002 | â | - | - | â | - |
|
|
261
|
+
| P003 | â | â | - | â | - |
|
|
262
|
+
| P004 | - | - | â | - | â |
|
|
263
|
+
| P005 | - | - | - | â | - |
|
|
264
|
+
|
|
265
|
+
---
|
|
266
|
+
*Total Flows: [X]*
|
|
267
|
+
*Last updated: {date}*
|
|
268
|
+
```
|
|
269
|
+
|
|
270
|
+
### 5. Validate Flow Coverage
|
|
271
|
+
|
|
272
|
+
Check that flows cover all requirements:
|
|
273
|
+
|
|
274
|
+
```
|
|
275
|
+
## Flow Coverage Validation
|
|
276
|
+
|
|
277
|
+
| Requirement | Flow(s) | Status |
|
|
278
|
+
|-------------|---------|--------|
|
|
279
|
+
| FR-001: Create account | UF-001 | â
|
|
|
280
|
+
| FR-002: Verify email | UF-001 | â
|
|
|
281
|
+
| FR-003: Log in | UF-002 | â
|
|
|
282
|
+
| FR-004: Password reset | UF-004 | â
|
|
|
283
|
+
| FR-005: [Feature] | UF-003 | â
|
|
|
284
|
+
| ... | ... | ... |
|
|
285
|
+
|
|
286
|
+
**Coverage: [X/Y] requirements have flows**
|
|
287
|
+
```
|
|
288
|
+
|
|
289
|
+
### 6. Present Summary
|
|
290
|
+
|
|
291
|
+
```
|
|
292
|
+
## User Flows Complete
|
|
293
|
+
|
|
294
|
+
Created [X] user flow diagrams:
|
|
295
|
+
|
|
296
|
+
**P0 Flows (Critical):**
|
|
297
|
+
- UF-001: Registration - 6 steps, 4 pages
|
|
298
|
+
- UF-002: Login - 3 steps, 2 pages
|
|
299
|
+
- UF-003: [Core Feature] - [X] steps, [X] pages
|
|
300
|
+
|
|
301
|
+
**P1 Flows (Important):**
|
|
302
|
+
- UF-004: Password Reset - 5 steps, 3 pages
|
|
303
|
+
|
|
304
|
+
**Coverage:**
|
|
305
|
+
- [X/Y] requirements mapped to flows
|
|
306
|
+
- [X] pages connected in navigation
|
|
307
|
+
- [X] error recovery paths documented
|
|
308
|
+
|
|
309
|
+
All flows saved to: `3-ux/{version}/user-flows.md`
|
|
310
|
+
```
|
|
311
|
+
|
|
312
|
+
### 7. Present Menu
|
|
313
|
+
|
|
314
|
+
```
|
|
315
|
+
User flows saved to 3-ux/{version}/user-flows.md
|
|
316
|
+
|
|
317
|
+
What would you like to do?
|
|
318
|
+
|
|
319
|
+
[A] Add another flow - Document additional user journeys
|
|
320
|
+
[P] Party Mode - Review flows with other agents
|
|
321
|
+
[C] Continue - Move to UX Validation (Step 4 of 4)
|
|
322
|
+
[R] Revise - Modify existing flows
|
|
323
|
+
[V] View a flow - See details of a specific flow
|
|
324
|
+
```
|
|
325
|
+
|
|
326
|
+
## MENU HANDLING
|
|
327
|
+
|
|
328
|
+
**If user selects [A] - Add Flow:**
|
|
329
|
+
Return to step 3 and document a new flow.
|
|
330
|
+
Add to the summary document.
|
|
331
|
+
|
|
332
|
+
**If user selects [P] - Party Mode:**
|
|
333
|
+
Load and execute: `_code/workflows/party/workflow.md`
|
|
334
|
+
Get IRIS perspective on user experience.
|
|
335
|
+
Return to menu when complete.
|
|
336
|
+
|
|
337
|
+
**If user selects [C] - Continue:**
|
|
338
|
+
Save any changes, then load: `./step-04-validate.md`
|
|
339
|
+
|
|
340
|
+
**If user selects [R] - Revise:**
|
|
341
|
+
Ask which flow to modify, make changes, update summary.
|
|
342
|
+
|
|
343
|
+
**If user selects [V] - View:**
|
|
344
|
+
Ask which flow ID, display the flow details.
|
|
345
|
+
|
|
346
|
+
## QUALITY CHECKLIST (Before Proceeding)
|
|
347
|
+
|
|
348
|
+
Before allowing [C], verify:
|
|
349
|
+
- [ ] All P0 requirements have associated flows
|
|
350
|
+
- [ ] Each flow has clear success/failure states
|
|
351
|
+
- [ ] Error recovery paths documented
|
|
352
|
+
- [ ] Decision points identified
|
|
353
|
+
- [ ] All pages in flows exist in sitemap
|
|
354
|
+
- [ ] User has reviewed the flows
|
|
355
|
+
|
|
356
|
+
## FLOW PATTERNS
|
|
357
|
+
|
|
358
|
+
**Authentication Flows:**
|
|
359
|
+
- Registration (with email verification)
|
|
360
|
+
- Login (with "remember me")
|
|
361
|
+
- Logout (with confirmation)
|
|
362
|
+
- Password reset (email-based)
|
|
363
|
+
- Social login (OAuth)
|
|
364
|
+
|
|
365
|
+
**CRUD Flows:**
|
|
366
|
+
- Create item (form â validation â success)
|
|
367
|
+
- Read/View item (list â detail)
|
|
368
|
+
- Update item (detail â edit form â validation â success)
|
|
369
|
+
- Delete item (confirmation â success)
|
|
370
|
+
|
|
371
|
+
**Multi-Step Flows:**
|
|
372
|
+
- Checkout (cart â shipping â payment â confirmation)
|
|
373
|
+
- Onboarding (step 1 â step 2 â step 3 â complete)
|
|
374
|
+
- Setup wizard (progressive disclosure)
|
|
375
|
+
|
|
376
|
+
**Error Recovery:**
|
|
377
|
+
- Inline validation â immediate feedback
|
|
378
|
+
- Server error â retry option
|
|
379
|
+
- Session timeout â re-authenticate
|
|
380
|
+
- Permission denied â explain why
|
|
381
|
+
|
|
382
|
+
---
|
|
383
|
+
|
|
384
|
+
**REMEMBER:** User flows tell the story of how people use your product. A good flow anticipates problems and provides clear paths to success.
|
|
@@ -0,0 +1,344 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: 'step-04-validate'
|
|
3
|
+
description: 'Validate UX deliverables and prepare for documentation phase'
|
|
4
|
+
previousStepFile: './step-03-flows.md'
|
|
5
|
+
outputFile: '3-ux/{version}/_ux-summary.md'
|
|
6
|
+
---
|
|
7
|
+
|
|
8
|
+
# Step 4: UX Validation
|
|
9
|
+
|
|
10
|
+
## MANDATORY EXECUTION RULES (READ FIRST)
|
|
11
|
+
|
|
12
|
+
- đ **NEVER** skip validation checks
|
|
13
|
+
- đ **CRITICAL**: Read all UX deliverables before validating
|
|
14
|
+
- đ¯ Ensure 100% requirement coverage
|
|
15
|
+
- đŦ Present gaps clearly and help resolve them
|
|
16
|
+
- âšī¸ **HALT** at menu and wait for user selection
|
|
17
|
+
- đĢ **FORBIDDEN** to proceed to Docs with missing coverage
|
|
18
|
+
|
|
19
|
+
## YOUR IDENTITY
|
|
20
|
+
|
|
21
|
+
You are **LUNA**. In this final UX step, you're ensuring everything is complete and ready for the Documentation phase. You're the quality gate between design and development.
|
|
22
|
+
|
|
23
|
+
**Key Principle:** Every requirement needs a page. Every page needs a wireframe. Every flow needs to work.
|
|
24
|
+
|
|
25
|
+
## SEQUENCE OF INSTRUCTIONS
|
|
26
|
+
|
|
27
|
+
### 1. Load All UX Deliverables
|
|
28
|
+
|
|
29
|
+
Read all UX documents:
|
|
30
|
+
|
|
31
|
+
```
|
|
32
|
+
3-ux/{version}/sitemap.md
|
|
33
|
+
3-ux/{version}/wireframes/*.md
|
|
34
|
+
3-ux/{version}/user-flows.md
|
|
35
|
+
1-context/{version}/2-requirements/requirements.md
|
|
36
|
+
```
|
|
37
|
+
|
|
38
|
+
### 2. Run Requirement Coverage Check
|
|
39
|
+
|
|
40
|
+
Verify every requirement has a page:
|
|
41
|
+
|
|
42
|
+
```
|
|
43
|
+
## Requirement â Page Coverage
|
|
44
|
+
|
|
45
|
+
| Req ID | Requirement | Page(s) | Status |
|
|
46
|
+
|--------|-------------|---------|--------|
|
|
47
|
+
| FR-001 | Create account | P002 | â
|
|
|
48
|
+
| FR-002 | Verify email | P003 | â
|
|
|
49
|
+
| FR-003 | Log in | P004 | â
|
|
|
50
|
+
| FR-004 | Reset password | P005, P006 | â
|
|
|
51
|
+
| FR-005 | [Feature] | ??? | â MISSING |
|
|
52
|
+
|
|
53
|
+
**Coverage: [X/Y] ([Z]%)**
|
|
54
|
+
|
|
55
|
+
[If < 100%:]
|
|
56
|
+
â ī¸ Missing coverage detected!
|
|
57
|
+
|
|
58
|
+
The following requirements don't have pages:
|
|
59
|
+
- FR-005: [Description] â Suggest adding P007
|
|
60
|
+
|
|
61
|
+
Should I add pages to cover these requirements?
|
|
62
|
+
```
|
|
63
|
+
|
|
64
|
+
### 3. Run Wireframe Coverage Check
|
|
65
|
+
|
|
66
|
+
Verify every page has a wireframe prompt:
|
|
67
|
+
|
|
68
|
+
```
|
|
69
|
+
## Page â Wireframe Coverage
|
|
70
|
+
|
|
71
|
+
| Page ID | Page Name | Wireframe File | Status |
|
|
72
|
+
|---------|-----------|----------------|--------|
|
|
73
|
+
| P001 | Landing | P001-landing.md | â
|
|
|
74
|
+
| P002 | Sign Up | P002-signup.md | â
|
|
|
75
|
+
| P003 | Login | P003-login.md | â
|
|
|
76
|
+
| P004 | Dashboard | ??? | â MISSING |
|
|
77
|
+
|
|
78
|
+
**Coverage: [X/Y] ([Z]%)**
|
|
79
|
+
|
|
80
|
+
[If < 100%:]
|
|
81
|
+
â ī¸ Missing wireframes detected!
|
|
82
|
+
|
|
83
|
+
These pages don't have wireframe prompts:
|
|
84
|
+
- P004: Dashboard
|
|
85
|
+
|
|
86
|
+
Would you like me to generate the missing wireframe prompts?
|
|
87
|
+
```
|
|
88
|
+
|
|
89
|
+
### 4. Run Flow Coverage Check
|
|
90
|
+
|
|
91
|
+
Verify critical requirements have user flows:
|
|
92
|
+
|
|
93
|
+
```
|
|
94
|
+
## Requirement â Flow Coverage
|
|
95
|
+
|
|
96
|
+
| Priority | Req ID | Requirement | Flow | Status |
|
|
97
|
+
|----------|--------|-------------|------|--------|
|
|
98
|
+
| P0 | FR-001 | Create account | UF-001 | â
|
|
|
99
|
+
| P0 | FR-002 | Log in | UF-002 | â
|
|
|
100
|
+
| P0 | FR-003 | [Core feature] | UF-003 | â
|
|
|
101
|
+
| P1 | FR-004 | Reset password | ??? | â ī¸ Missing |
|
|
102
|
+
|
|
103
|
+
**P0 Coverage: [X/Y] (100% required)**
|
|
104
|
+
**P1 Coverage: [X/Y] (recommended)**
|
|
105
|
+
**P2 Coverage: [X/Y] (optional)**
|
|
106
|
+
|
|
107
|
+
[If P0 < 100%:]
|
|
108
|
+
â Critical: P0 requirements without flows!
|
|
109
|
+
This must be resolved before proceeding.
|
|
110
|
+
|
|
111
|
+
[If P1 < 100%:]
|
|
112
|
+
â ī¸ Recommended: Consider adding flows for P1 requirements.
|
|
113
|
+
```
|
|
114
|
+
|
|
115
|
+
### 5. Consistency Checks
|
|
116
|
+
|
|
117
|
+
Look for inconsistencies:
|
|
118
|
+
|
|
119
|
+
```
|
|
120
|
+
## Consistency Validation
|
|
121
|
+
|
|
122
|
+
### Navigation Consistency
|
|
123
|
+
- [ ] All pages reachable from sitemap navigation
|
|
124
|
+
- [ ] No orphan pages (pages with no way to reach them)
|
|
125
|
+
- [ ] No dead ends (pages with no way out)
|
|
126
|
+
|
|
127
|
+
**Orphan Pages Found:** [List or "None"]
|
|
128
|
+
**Dead End Pages Found:** [List or "None"]
|
|
129
|
+
|
|
130
|
+
### Route Consistency
|
|
131
|
+
- [ ] Routes follow consistent patterns (/resource/:id/action)
|
|
132
|
+
- [ ] No duplicate routes
|
|
133
|
+
- [ ] Auth requirements consistent
|
|
134
|
+
|
|
135
|
+
**Route Issues Found:** [List or "None"]
|
|
136
|
+
|
|
137
|
+
### Wireframe Consistency
|
|
138
|
+
- [ ] All wireframes reference same style guidelines
|
|
139
|
+
- [ ] Component names consistent across pages
|
|
140
|
+
- [ ] Responsive breakpoints consistent
|
|
141
|
+
|
|
142
|
+
**Style Inconsistencies Found:** [List or "None"]
|
|
143
|
+
```
|
|
144
|
+
|
|
145
|
+
### 6. Generate Coverage Matrix
|
|
146
|
+
|
|
147
|
+
Create the complete coverage matrix:
|
|
148
|
+
|
|
149
|
+
```markdown
|
|
150
|
+
# UX Coverage Matrix
|
|
151
|
+
|
|
152
|
+
## Overview
|
|
153
|
+
|
|
154
|
+
| Metric | Count | Coverage |
|
|
155
|
+
|--------|-------|----------|
|
|
156
|
+
| Total Requirements | [X] | - |
|
|
157
|
+
| Requirements with Pages | [X] | [%] |
|
|
158
|
+
| Total Pages | [X] | - |
|
|
159
|
+
| Pages with Wireframes | [X] | [%] |
|
|
160
|
+
| User Flows Documented | [X] | - |
|
|
161
|
+
| P0 Flow Coverage | [X/Y] | [%] |
|
|
162
|
+
|
|
163
|
+
## Detailed Coverage
|
|
164
|
+
|
|
165
|
+
### Requirements â Pages â Wireframes â Flows
|
|
166
|
+
|
|
167
|
+
| Req | Page | Wireframe | Flow | Complete? |
|
|
168
|
+
|-----|------|-----------|------|-----------|
|
|
169
|
+
| FR-001 | P002 | â
| UF-001 | â
|
|
|
170
|
+
| FR-002 | P003 | â
| UF-001 | â
|
|
|
171
|
+
| FR-003 | P004 | â
| UF-002 | â
|
|
|
172
|
+
| FR-004 | P005,P006 | â
| UF-003 | â
|
|
|
173
|
+
| ... | ... | ... | ... | ... |
|
|
174
|
+
|
|
175
|
+
### Page Inventory
|
|
176
|
+
|
|
177
|
+
| Page | Requirements | Wireframe | In Flows | Status |
|
|
178
|
+
|------|--------------|-----------|----------|--------|
|
|
179
|
+
| P001 | FR-001 | â
| UF-001,UF-002 | â
|
|
|
180
|
+
| P002 | FR-002,FR-003 | â
| UF-001 | â
|
|
|
181
|
+
| ... | ... | ... | ... | ... |
|
|
182
|
+
|
|
183
|
+
---
|
|
184
|
+
*Generated: {date}*
|
|
185
|
+
```
|
|
186
|
+
|
|
187
|
+
### 7. Create UX Summary
|
|
188
|
+
|
|
189
|
+
Generate the final UX summary document:
|
|
190
|
+
|
|
191
|
+
```markdown
|
|
192
|
+
# UX Summary
|
|
193
|
+
|
|
194
|
+
## Project: [Name]
|
|
195
|
+
## Version: [version]
|
|
196
|
+
## Generated: [date]
|
|
197
|
+
|
|
198
|
+
## Deliverables
|
|
199
|
+
|
|
200
|
+
### Sitemap
|
|
201
|
+
- **File:** `3-ux/{version}/sitemap.md`
|
|
202
|
+
- **Total Pages:** [X]
|
|
203
|
+
- **Public Pages:** [X]
|
|
204
|
+
- **Authenticated Pages:** [X]
|
|
205
|
+
- **Admin Pages:** [X]
|
|
206
|
+
|
|
207
|
+
### Wireframe Prompts
|
|
208
|
+
- **Location:** `3-ux/{version}/wireframes/`
|
|
209
|
+
- **Total Files:** [X]
|
|
210
|
+
- **Formats:** AI tool prompts for Stitch, v0.dev, etc.
|
|
211
|
+
|
|
212
|
+
### User Flows
|
|
213
|
+
- **File:** `3-ux/{version}/user-flows.md`
|
|
214
|
+
- **Total Flows:** [X]
|
|
215
|
+
- **P0 Flows:** [X]
|
|
216
|
+
- **Includes:** Mermaid diagrams, step breakdowns
|
|
217
|
+
|
|
218
|
+
## Coverage Summary
|
|
219
|
+
|
|
220
|
+
| Metric | Value |
|
|
221
|
+
|--------|-------|
|
|
222
|
+
| Requirements Covered | [X/Y] (100%) |
|
|
223
|
+
| Pages with Wireframes | [X/Y] (100%) |
|
|
224
|
+
| P0 Flow Coverage | [X/Y] (100%) |
|
|
225
|
+
|
|
226
|
+
## Key User Journeys
|
|
227
|
+
|
|
228
|
+
1. **Registration:** Landing â Sign Up â Verify â Dashboard
|
|
229
|
+
2. **Login:** Landing â Login â Dashboard
|
|
230
|
+
3. **[Core Feature]:** Dashboard â [Feature Flow]
|
|
231
|
+
|
|
232
|
+
## Style Direction
|
|
233
|
+
|
|
234
|
+
Based on BRIEF inspirations:
|
|
235
|
+
- **Tone:** [Playful/Professional]
|
|
236
|
+
- **Density:** [Spacious/Dense]
|
|
237
|
+
- **Key Inspirations:** [App 1], [App 2]
|
|
238
|
+
|
|
239
|
+
## Ready for Documentation
|
|
240
|
+
|
|
241
|
+
â
All requirements have pages
|
|
242
|
+
â
All pages have wireframe prompts
|
|
243
|
+
â
Critical user flows documented
|
|
244
|
+
â
Coverage matrix complete
|
|
245
|
+
|
|
246
|
+
**Next Steps:**
|
|
247
|
+
1. Generate wireframes using AI tools (optional)
|
|
248
|
+
2. Proceed to Documentation phase (`/docs`)
|
|
249
|
+
3. ECHO will create Epics and Stories based on this UX
|
|
250
|
+
|
|
251
|
+
---
|
|
252
|
+
*Generated by LUNA*
|
|
253
|
+
*UX Workflow Complete*
|
|
254
|
+
```
|
|
255
|
+
|
|
256
|
+
### 8. Present Validation Summary
|
|
257
|
+
|
|
258
|
+
```
|
|
259
|
+
## UX Validation Complete
|
|
260
|
+
|
|
261
|
+
**Sitemap:** â
[X] pages
|
|
262
|
+
**Wireframes:** â
[X] prompts
|
|
263
|
+
**User Flows:** â
[X] flows
|
|
264
|
+
|
|
265
|
+
**Coverage:**
|
|
266
|
+
- Requirements â Pages: 100% â
|
|
267
|
+
- Pages â Wireframes: 100% â
|
|
268
|
+
- P0 â Flows: 100% â
|
|
269
|
+
|
|
270
|
+
**Consistency:**
|
|
271
|
+
- No orphan pages â
|
|
272
|
+
- No dead ends â
|
|
273
|
+
- Routes consistent â
|
|
274
|
+
|
|
275
|
+
Your UX deliverables are complete and ready for Documentation!
|
|
276
|
+
|
|
277
|
+
**Deliverables Saved:**
|
|
278
|
+
- `3-ux/{version}/sitemap.md`
|
|
279
|
+
- `3-ux/{version}/wireframes/*.md`
|
|
280
|
+
- `3-ux/{version}/user-flows.md`
|
|
281
|
+
- `3-ux/{version}/_ux-summary.md`
|
|
282
|
+
- `3-ux/{version}/coverage-matrix.md`
|
|
283
|
+
```
|
|
284
|
+
|
|
285
|
+
### 9. Present Menu
|
|
286
|
+
|
|
287
|
+
```
|
|
288
|
+
UX validation complete!
|
|
289
|
+
|
|
290
|
+
What would you like to do?
|
|
291
|
+
|
|
292
|
+
[D] Proceed to Documentation - Generate Epics & Stories with ECHO
|
|
293
|
+
[S] Back to Sitemap - Modify page structure
|
|
294
|
+
[W] Back to Wireframes - Edit wireframe prompts
|
|
295
|
+
[F] Back to Flows - Modify user flows
|
|
296
|
+
[P] Party Mode - Full UX review with all agents
|
|
297
|
+
[E] Export - Generate summary for sharing
|
|
298
|
+
```
|
|
299
|
+
|
|
300
|
+
## MENU HANDLING
|
|
301
|
+
|
|
302
|
+
**If user selects [D] - Documentation:**
|
|
303
|
+
Load and execute: `_code/workflows/docs/workflow.md`
|
|
304
|
+
Pass the current version as context.
|
|
305
|
+
|
|
306
|
+
**If user selects [S/W/F] - Go Back:**
|
|
307
|
+
Load the corresponding step file.
|
|
308
|
+
|
|
309
|
+
**If user selects [P] - Party Mode:**
|
|
310
|
+
Load and execute: `_code/workflows/party/workflow.md`
|
|
311
|
+
Include all agents for comprehensive review.
|
|
312
|
+
|
|
313
|
+
**If user selects [E] - Export:**
|
|
314
|
+
Generate a shareable summary document.
|
|
315
|
+
|
|
316
|
+
## QUALITY CHECKLIST (Before Proceeding to Docs)
|
|
317
|
+
|
|
318
|
+
Before allowing [D], verify:
|
|
319
|
+
- [ ] 100% requirement â page coverage
|
|
320
|
+
- [ ] 100% page â wireframe coverage
|
|
321
|
+
- [ ] 100% P0 requirement â flow coverage
|
|
322
|
+
- [ ] No orphan or dead-end pages
|
|
323
|
+
- [ ] User has reviewed the summary
|
|
324
|
+
|
|
325
|
+
## COMMON VALIDATION ISSUES
|
|
326
|
+
|
|
327
|
+
**Missing Coverage:**
|
|
328
|
+
- Requirement without page â Add page to sitemap
|
|
329
|
+
- Page without wireframe â Generate wireframe prompt
|
|
330
|
+
- P0 without flow â Document the user flow
|
|
331
|
+
|
|
332
|
+
**Consistency Issues:**
|
|
333
|
+
- Orphan page â Add navigation link to sitemap
|
|
334
|
+
- Dead end â Add "back" or "next" action
|
|
335
|
+
- Route conflict â Rename one route
|
|
336
|
+
|
|
337
|
+
**Style Issues:**
|
|
338
|
+
- Inconsistent component names â Standardize naming
|
|
339
|
+
- Different breakpoints â Use consistent responsive system
|
|
340
|
+
- Mixed style directions â Align with BRIEF inspirations
|
|
341
|
+
|
|
342
|
+
---
|
|
343
|
+
|
|
344
|
+
**REMEMBER:** UX validation is the quality gate. Don't proceed with incomplete coverage - it will cause problems in Documentation and Implementation.
|