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.4 KiB
1.4 KiB
id, title, status, date, parent
| id | title | status | date | parent |
|---|---|---|---|---|
| 3-6 | 3-6 Calendar File Generation (.ics) | QA Review | 2026-09-27 | 3 |
Description
As a client, I want to receive a calendar file when my booking is approved, So that I can easily add the consultation to my calendar app. Context: Integrates with: Consultation model, email attachments; Technology: iCalendar format (RFC 5545); Follows pattern: Service class for generation. Full implementation history: docs/stories/story-3.6-calendar-file-generation.md
Acceptance Criteria
- Generate valid .ics file on booking approval
- File follows iCalendar specification (RFC 5545)
- Compatible with major calendar apps:
- Event title: "Consultation with Libra Law Firm" (bilingual)
- Date and time (correct timezone)
- Duration: 45 minutes
- Location (office address or "Phone consultation")
- Description with:
- Reminder: 1 hour before
- Attach to approval email
- Available for download from client dashboard
- Proper MIME type (text/calendar)
- Correct filename (consultation-{date}.ics)
- Event title in client's preferred language
- Description in client's preferred language
- Valid iCalendar format (passes validators)
- Tests for file generation
- Tests for calendar app compatibility
- Tests for bilingual content (Arabic/English)
- Tests for download route authorization
- Tests for email attachment