care-api/.orchestrator/task_agent_mapping.md

🎯 Task-Agent Mapping - care-api Orchestration

Project: KiviCare REST API WordPress Plugin
Total Tasks: 62
Orchestration Strategy: Specialized agent assignment with parallel execution
Technology Stack: PHP 8.1+, WordPress 6.3+, JWT, KiviCare, PHPUnit

---

🤖 AGENT SPECIALIZATION MATRIX

WordPress Plugin Development

• wordpress-plugin-developer - WordPress-specific patterns, hooks, filters
• php-fullstack-engineer - PHP backend development, database operations
• dev-helper - Testing, debugging, code quality

Security & Authentication

• security-compliance-specialist - JWT security, HIPAA compliance, validation
• database-design-specialist - Database schema, queries, optimization

Testing & Quality Assurance

• dev-helper - Unit tests, integration tests, contract tests
• performance-optimization-engineer - Performance testing, optimization

---

📋 PHASE 3.1: SETUP & FOUNDATION

T001-T006: WordPress Plugin Foundation

Agent: wordpress-plugin-developer
Rationale: WordPress plugin structure, activation hooks, REST API namespace registration Parallel Execution: T003-T004 can run in parallel (different files)

T001: WordPress plugin directory structure → wordpress-plugin-developer
T002: composer.json setup → wordpress-plugin-developer  
T003: [P] PHPUnit configuration → dev-helper
T004: [P] WordPress coding standards → dev-helper
T005: Plugin activation/deactivation hooks → wordpress-plugin-developer
T006: REST API namespace registration → wordpress-plugin-developer

---

📋 PHASE 3.2: TESTS FIRST (TDD)

T007-T016: Contract Tests (API Endpoints)

Agent: dev-helper
Rationale: Specialized in TDD patterns, API contract testing, WordPress testing framework Parallel Execution: ALL tasks can run in parallel (different test files)

# Authentication Endpoints
T007: [P] POST /auth/login contract test → dev-helper

# Clinic Endpoints  
T008: [P] GET /clinics contract test → dev-helper
T009: [P] POST /clinics contract test → dev-helper

# Patient Endpoints
T010: [P] GET /patients contract test → dev-helper
T011: [P] POST /patients contract test → dev-helper

# Appointment Endpoints
T012: [P] GET /appointments contract test → dev-helper
T013: [P] POST /appointments contract test → dev-helper

# Encounter Endpoints
T014: [P] GET /encounters contract test → dev-helper
T015: [P] POST /encounters contract test → dev-helper

# Prescription Endpoints
T016: [P] POST /encounters/{id}/prescriptions contract test → dev-helper

T017-T021: Integration Tests (User Stories)

Agent: dev-helper
Rationale: Complex workflow testing requiring WordPress integration expertise Parallel Execution: ALL tasks can run in parallel (different workflow scenarios)

T017: [P] Doctor creates patient record workflow → dev-helper
T018: [P] Doctor creates encounter with prescriptions → dev-helper
T019: [P] Multi-doctor clinic data access → dev-helper
T020: [P] Automatic billing generation → dev-helper
T021: [P] Role-based access control → dev-helper

---

📋 PHASE 3.3: CORE IMPLEMENTATION

T022-T029: Entity Models

Agent: php-fullstack-engineer
Rationale: PHP OOP expertise, WordPress database integration, validation logic Parallel Execution: ALL tasks can run in parallel (independent model classes)

T022: [P] Clinic model class → php-fullstack-engineer
T023: [P] Patient model class → php-fullstack-engineer
T024: [P] Doctor model class → php-fullstack-engineer
T025: [P] Appointment model class → php-fullstack-engineer
T026: [P] Encounter model class → php-fullstack-engineer
T027: [P] Prescription model class → php-fullstack-engineer
T028: [P] Bill model class → php-fullstack-engineer
T029: [P] Service model class → php-fullstack-engineer

T030-T032: Authentication & Authorization

Agent: security-compliance-specialist
Rationale: JWT security expertise, healthcare compliance, role-based access Sequential Execution: Dependencies between JWT → Permissions → Session

T030: JWT authentication service → security-compliance-specialist
T031: Role-based permission service → security-compliance-specialist (after T030)
T032: User session management → security-compliance-specialist (after T031)

T033-T039: Database Services

Agent: database-design-specialist
Rationale: Database operations, query optimization, WordPress $wpdb expertise Parallel Execution: ALL tasks can run in parallel (independent service classes)

T033: [P] Clinic database service → database-design-specialist
T034: [P] Patient database service → database-design-specialist
T035: [P] Doctor database service → database-design-specialist
T036: [P] Appointment database service → database-design-specialist
T037: [P] Encounter database service → database-design-specialist
T038: [P] Prescription database service → database-design-specialist
T039: [P] Bill database service → database-design-specialist

T040-T045: REST API Endpoints

Agent: php-fullstack-engineer
Rationale: REST API development, WordPress REST API framework, endpoint routing Sequential Dependencies: Auth endpoints first, then CRUD endpoints

T040: Authentication endpoints → php-fullstack-engineer
T041: Clinic CRUD endpoints → php-fullstack-engineer (after T040)
T042: Patient CRUD endpoints → php-fullstack-engineer (after T040)
T043: Appointment CRUD endpoints → php-fullstack-engineer (after T040)
T044: Encounter CRUD endpoints → php-fullstack-engineer (after T040)
T045: Prescription endpoints → php-fullstack-engineer (after T040)

T046-T048: Validation & Error Handling

Agent: security-compliance-specialist
Rationale: Input validation security, healthcare data protection, compliance logging Sequential Execution: Validator → Error Handler → Logger

T046: Input validation service → security-compliance-specialist
T047: Error response formatter → security-compliance-specialist (after T046)
T048: Request/response logging → security-compliance-specialist (after T047)

---

🔄 EXECUTION STRATEGY

Parallel Execution Groups

# Group 1: Foundation Setup (Parallel where marked)
wordpress-plugin-developer: T001, T002, T005, T006
dev-helper: T003, T004

# Group 2: All Contract Tests (Full Parallel)
dev-helper: T007-T016 (ALL in parallel)

# Group 3: All Integration Tests (Full Parallel) 
dev-helper: T017-T021 (ALL in parallel)

# Group 4: All Entity Models (Full Parallel)
php-fullstack-engineer: T022-T029 (ALL in parallel)

# Group 5: Authentication Chain (Sequential)
security-compliance-specialist: T030 → T031 → T032

# Group 6: All Database Services (Full Parallel)
database-design-specialist: T033-T039 (ALL in parallel)

# Group 7: API Endpoints (Auth first, then parallel)
php-fullstack-engineer: T040 → (T041, T042, T043, T044, T045 parallel)

# Group 8: Validation Chain (Sequential)
security-compliance-specialist: T046 → T047 → T048

Dependencies Management

• Phase Sequential: 3.1 → 3.2 → 3.3
• TDD Critical: All tests (T007-T021) MUST be written and failing before implementation (T022+)
• Authentication Dependency: T040 must complete before T041-T045
• Service Dependencies: Models (T022-T029) should complete before endpoints (T041-T045)

---

📊 ORCHESTRATION EFFICIENCY

Parallelization Opportunities

• Contract Tests: 10 parallel tasks (T007-T016)
• Integration Tests: 5 parallel tasks (T017-T021)
• Entity Models: 8 parallel tasks (T022-T029)
• Database Services: 7 parallel tasks (T033-T039)
• CRUD Endpoints: 5 parallel tasks (T041-T045)

Critical Path Analysis

Longest Sequential Chain: Authentication services (T030-T032) + Validation chain (T046-T048) = 6 sequential tasks

Agent Workload Distribution

• wordpress-plugin-developer: 4 tasks (foundation)
• dev-helper: 15 tasks (all testing)
• php-fullstack-engineer: 13 tasks (models + endpoints)
• security-compliance-specialist: 6 tasks (auth + validation)
• database-design-specialist: 7 tasks (database services)

---

🎯 EXECUTION GUARANTEES

Pre-execution Validation

1. ✅ WordPress plugin structure requirements verified
2. ✅ KiviCare dependency compatibility confirmed
3. ✅ PHP 8.1 + WordPress 6.3+ compatibility validated
4. ✅ JWT security requirements documented

TDD Enforcement

1. Fail-First Requirement: All tests T007-T021 must be written and failing
2. Implementation Block: Tasks T022+ cannot start until all tests are failing
3. Test-Green Requirement: Implementation must make tests pass

Quality Gates

1. WordPress Coding Standards: All code must pass WPCS validation
2. Security Validation: All authentication/validation code must pass security review
3. Performance Testing: All database operations must meet performance requirements

---

Task-Agent Mapping: ✅ Complete
Parallel Execution Strategy: ✅ Optimized
Dependency Management: ✅ Validated
Ready for Orchestrated Execution: ✅ APPROVED