[TASK][Roadmap] Recommended execution order for PRD implementation

[vugarsafarzada]

Purpose

This is the canonical execution-order issue for implementing the current Reziphay PRD across backend and frontend. Future AI/code agents should use this issue as the default sequencing reference before starting work.

Canonical Rules

• Prefer backend contract work before frontend integration for the same domain.
• Prefer lower phases before higher phases.
• A later issue may start early only if the required backend contract is already stable.
• "Stable" means either merged to main or the API/data contract is frozen enough that another agent can build on it safely.

Recommended Phase Order

Phase 1: Auth Foundation

1. nodejs-app#6 [TASK][Backend] Complete auth security flows
2. nextjs-app#6 [TASK][Frontend] Ship auth UX

Phase 2: Brand/Branch Foundation

1. nodejs-app#7 [TASK][Backend] Finish brand and branch business rules
2. nextjs-app#7 [TASK][Frontend] Build the USO brand and branch workspace

Phase 3: Service Foundation + Discovery Base

1. nodejs-app#9 [TASK][Backend] Introduce the service domain
2. nextjs-app#9 [TASK][Frontend] Build service authoring
3. nextjs-app#10 [TASK][Frontend] Build discovery/detail experiences

Phase 4: Moderation Layer

1. nodejs-app#11 [TASK][Backend] Add admin moderation APIs
2. nextjs-app#13 [TASK][Frontend] Build the admin moderation workspace

Phase 5: Team Ecosystem

1. nodejs-app#8 [TASK][Backend] Expand branch team workflows
2. nextjs-app#8 [TASK][Frontend] Build the branch team workspace

Phase 6: Reservation Core

1. nodejs-app#10 [TASK][Backend] Introduce reservation and availability APIs
2. nextjs-app#11 [TASK][Frontend] Build the reservation booking flow

Phase 7: Post-Booking Operations

1. nodejs-app#12 [TASK][Backend] Expand notifications and post-completion reviews
2. nextjs-app#12 [TASK][Frontend] Build reservation management, notifications, and reviews

Default Single-Agent Order

If only one agent is working at a time, use this exact order:

1. nodejs-app#6
2. nextjs-app#6
3. nodejs-app#7
4. nextjs-app#7
5. nodejs-app#9
6. nextjs-app#9
7. nextjs-app#10
8. nodejs-app#11
9. nextjs-app#13
10. nodejs-app#8
11. nextjs-app#8
12. nodejs-app#10
13. nextjs-app#11
14. nodejs-app#12
15. nextjs-app#12

Safe Parallel Windows

• After nodejs-app#6 stabilizes, nextjs-app#6 can start while backend moves into #7.
• After nodejs-app#9 stabilizes, nextjs-app#9 and nextjs-app#10 can run in parallel if different agents own different files/components.
• After nodejs-app#11 stabilizes, nextjs-app#13 can run while backend moves into #8.
• After nodejs-app#10 stabilizes, nextjs-app#11 can run while backend starts #12, as long as reservation payloads are not changing underneath the frontend.

Start Here

If an agent is picking up the project cold, start with nodejs-app#6 unless that issue is already fully closed and merged.