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.4 KiB
1.4 KiB
id, title, status, date, parent
| id | title | status | date | parent |
|---|---|---|---|---|
| 8-9 | 8-9 Admin Notification - New Booking | QA Review | 2026-09-27 | 8 |
Description
As an admin, I want to be notified when a client submits a booking request, So that I can review and respond promptly. Using Mailable pattern to align with sibling stories (8.2-8.8):. Full implementation history: docs/stories/story-8.9-admin-notification-new-booking.md
Acceptance Criteria
- Sent immediately after successful consultation creation (same trigger as Story 8.3)
- Consultation status: pending
- Email queued for async delivery
- First user with
user_type = 'admin'in the database - If no admin exists, log error but don't fail the booking process
- Subject line: "[Action Required] New Consultation Request" / "[إجراء مطلوب] طلب استشارة جديد"
- "New Consultation Request" heading
- Client name:
- Requested date and time (formatted per admin's language preference)
- Problem summary (full text, no truncation)
- Client contact information:
- "Review Request" button linking to consultation detail in admin dashboard
- "[Action Required]" prefix in subject line (English)
- "[إجراء مطلوب]" prefix in subject line (Arabic)
- Email sent in admin's
preferred_language - Default to 'en' (English) if admin has no preference set (admin-facing communications default to English)