DES-05 — Day 5 — Screen inventory validation, user flows & wireframes
Validate the inventory on this site (count, features per screen, states), draw the reseller, delegate and back-office flows, wireframe checkout, the visit flow and tour closing.
| Field | Details |
|---|---|
| Task code | DES-05 |
| Phase | P0 — Foundations (cadrage, UX/UI, architecture & contract) |
| Product scope | V1 |
| Status | Planned |
| Start | Thu 22 Oct 2026 |
| Due | Thu 22 Oct 2026 |
| Responsible | Akram — UI/UX designer |
| Co-responsible | Anis, Imad |
| Effort | 1 person-day(s) planned · 1.25 from scratch · size S |
| Area · app | UX · design |
| Depends on | DES-01 |
| Unblocks | DES-06 |
| Milestones | Screen inventory frozen |
Summary
Validate the inventory on this site (count, features per screen, states), draw the reseller, delegate and back-office flows, wireframe checkout, the visit flow and tour closing.
Description
Day 5 freezes the list of screens before the 15 screen days start. Akram, Imad (RA, DA) and Anis (BO, RW) walk the inventory on /docs/design/screen-inventory together: 155 screens, 146 V1 and 9 V2 (RA-01…41, DA-01…28, BO-01…71, RW-01…15). For each screen they check the count, features, data (API op ids), states, French names, navigation and requirement coverage. Akram also draws the four user flows and low-fidelity wireframes of the three riskiest flows: checkout, the visit flow and tour closing. The result is the milestone « Screen inventory frozen » (client checkpoint 2); after it, changes go through change requests. Anis applies the agreed additions, merges and renames to screens.json so that every design day (DES-06…DES-20) and build task reads a stable list.
Subtasks
| # | Subtask | Owner |
|---|---|---|
| 1 | Walk the Day-5 checklist row by row: count per app, each V1 requirement with a UI mapped to at least one screen, data per screen (API op ids), states, French names, navigation entry points | Akram |
| 2 | Check that every 17 Oct surface is in the inventory: RA-41 guest mode, RA-13/RW-03 advanced filters, RA-32/RW-14 regional WhatsApp, RA-33/BO-56 after-sales, RA-40/BO-69 returns, BO-41 orders to confirm, BO-70 support regions, BO-71 attributes, live status on RA-21/22 and RW-08/09 | Akram |
| 3 | Decide BO-31 « Price lists & agreements »: rename it to a bulk editor of the three prices with PriceChange history, or move it to V2 (PRC-03). Then update screens.json (adds, merges, renames) | Anis |
| 4 | Flag mobile build-task mismatches (RA-36 and DA-28 under MOB-05/MOB-10, DA-01…03 built from the Day-6 variants) and confirm the states list of each mobile screen | Imad |
| 5 | Flow 1 — reseller ordering: RA-02 guest → RA-12/13 → RA-14 price lock → RA-03 → RA-04 → RA-05 → RA-06 pending → RA-17 → RA-18 → RA-20 « Envoyée » → RA-22 live tracking | Akram |
| 6 | Flow 2 — delegate day: DA-05 → DA-06 start → DA-08 navigate and arrive → DA-10 visit → DA-12 report (or DA-11 not done) → DA-14/16/17 conversion → DA-20 closing → DA-27 sync | Akram |
| 7 | Flow 3 — back-office confirmation and delivery: BO-41 queue → BO-39 controls (confirm, hold, refuse, modify) → BO-42 kanban → delivered with proof. Flow 4 — after-sales and returns: RA-22 → RA-33 claim / RA-40 return → BO-56 / BO-69 diagnosis → resolution (replacement order, return, credit note, repair, rejected) → reception with automatic restock | Akram |
| 8 | Low-fidelity wireframes: checkout RA-17/RA-18 (minimum amount, payment methods including CREDIT, address, note, submit), visit flow DA-08 → DA-10 → DA-12, tour closing DA-20 (blockers, summary, comment, confirmation) | Akram |
| 9 | Client checkpoint 2 (45 min): inventory, V1/V2 split (loyalty, packs and detailed credit are V2; returns and after-sales are V1), the four flows. Additions become change requests | Akram |
Deliverables
- Frozen screen inventory: screens.json updated by Anis, /docs/design/screen-inventory marked frozen
- Claude Design section
00 · Flows & wireframesat the top of the Reseller App, Delegate App and Back-office pages (4 flows, 3 wireframes) - Day-5 checklist ticked, with decisions (including BO-31) in the decision register
- Checkpoint 2 notes confirming scope with HOCO
Acceptance criteria
- Every V1 requirement with a user interface maps to at least one screen; any orphan is justified in writing
- Every screen in screens.json has a design day and a build task
- The BO-31 decision is recorded and screens.json reflects it
- The four flows run end to end with a screen id on every node, including error branches (minimum amount, credit exceeded, GPS out of tolerance, unsynced items)
- Imad and Anis sign off in the session, recorded in the checklist
Test measures
- Requirement-coverage check: every V1 requirement id with an app appears in some screen's
reqs - Walk each flow aloud with the developer who builds it; each step names its API operation
- Confirm the V1/V2 split with HOCO at checkpoint 2
Risks
- HOCO adds screens at checkpoint 2 — accept them only as change requests with an effort estimate; the buffer is DES-22.
- Imad and Anis cannot give a full day — time-box 2 h with each, and handle the rest asynchronously in comments on the shared design the same day.
KPI
- Delivered by Thu 22 Oct 2026 within 1 person-day(s).
- Every acceptance criterion above demonstrated before hand-off; linked requirements' acceptance criteria pass.
- Zero open critical defects, permission gaps or data-integrity regressions at sign-off.
Generated from content/plan/tasks.json by scripts/generate-team-tasks.mjs. Dates are computed by the scheduler (Sunday–Thursday weeks, holidays excluded) — change the plan, not this page.
DES-04 — Day 4 — Web & back-office components and page templates
Sidebar, top bar, data table with filters/bulk actions, forms, KPI cards, chart styles, drawers, modals, timeline, map markers, uploaders; list/detail/form/settings/dashboard page templates.
DES-06 — Day 6 — Reseller app: onboarding & account
Splash, welcome with guest browsing, guest price lock, sign-up (phone, OTP, store details, customer type), pending validation, sign-in, forgot password.