Naser Mansour
0f9d12c3cf
Adds docs/tasks/ (16 epics + 102 stories converted to task/subtask files with statuses.md as the new status source of truth) and docs/ux-design.md (retrospective design-system reference), and points CLAUDE.md at them. docs/prd.md and docs/architecture.md are kept as BMAD wrote them; the legacy docs/stories/, docs/epics/, docs/qa/gates/ and .bmad-core/ stay in place as historical/traceability records, superseded but not deleted. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
1.5 KiB
1.5 KiB
id, title, status, date, parent
| id | title | status | date | parent |
|---|---|---|---|---|
| 3-7 | 3-7 Consultation Management | QA Review | 2026-09-27 | 3 |
Description
As an admin, I want to manage consultations throughout their lifecycle, So that I can track completed sessions, handle no-shows, and maintain accurate records. Context: Integrates with: consultations table, notifications; Technology: Livewire Volt, Flux UI; Follows pattern: Admin management dashboard. Handle these scenarios with appropriate validation and error handling:. Full implementation history: docs/stories/story-3.7-consultation-management.md
Acceptance Criteria
- View all consultations with filters:
- Sort by date, status, client name
- Pagination (15/25/50 per page)
- Quick status indicators
- Mark consultation as completed
- Mark consultation as no-show
- Cancel booking on behalf of client
- Status change confirmation
- Reschedule appointment to new date/time
- Validate new slot availability
- Send notification to client
- Generate new .ics file
- Mark payment as received (for paid consultations)
- Payment date recorded
- Payment status visible in list
- Add internal admin notes
- Notes not visible to client
- View notes in consultation detail
- Edit/delete notes
- View all consultations for a specific client
- Linked from user profile
- Summary statistics per client
- Audit log for all status changes
- Bilingual labels
- Tests for status transitions