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.1 KiB
1.1 KiB
id, title, status, date, parent
| id | title | status | date | parent |
|---|---|---|---|---|
| 15-1 | 15-1 Database Schema & Model Setup | QA Review | 2026-09-27 | 15 |
Description
As an admin I want to have a database structure for potential clients So that I can store and manage prospective client information. Full implementation history: docs/stories/story-15.1-database-model.md
Acceptance Criteria
- AC1: Database Migration: Given the system needs to store potential clients; When the migration runs; Then a
potential_clientstable is created with: - AC2: PotentialClientType Enum: Given potential clients have different types; When the enum is created; Then
App\Enums\PotentialClientTypecontains: - AC3: PotentialClient Model: Given the migration exists; When the model is created; Then
App\Models\PotentialClientincludes: - AC4: Model Factory: Given tests need potential client data; When the factory is created; Then
Database\Factories\PotentialClientFactorygenerates: - AC5: Translation Keys: Given the system is bilingual; When translations are added; Then create keys in
lang/en/potential-clients.phpandlang/ar/potential-clients.php: