HOCO B2B
Team tasksAnis

PRJ-02 — Docs site, PRD/SRS baseline & delivery plan

This site: PRD, SRS, service catalogue, data model, API catalogue, screen inventory, ways of working and the scheduled plan.

FieldDetails
Task codePRJ-02
PhaseP0 — Foundations (cadrage, UX/UI, architecture & contract)
Product scopeV1
StatusDone (Sat 17 Oct 2026)
StartSat 17 Oct 2026
DueSat 17 Oct 2026
ResponsibleAnis — Full-stack developer
Co-responsible—
Effort1 person-day(s) planned · 6 from scratch · size S
Area · appProject · docs
Depends onPRJ-01
UnblocksPRJ-03, SRV-01
Milestones—

Summary

This site: PRD, SRS, service catalogue, data model, API catalogue, screen inventory, ways of working and the scheduled plan.

Description

Done on 17 Oct 2026. This task produced the documentation site (@hoco/docs, Fumadocs) as the single source the client, Akram, Imad and Anis work from, turning the cahier des charges v1.0 into actionable specifications. It delivered the PRD and user flows, the SRS (scope, glossary, ~190 requirements in 25 areas, lifecycles and statuses, business rules and settings, permissions matrix, notifications matrix, acceptance scenarios, open decisions, traceability to the cahier), the service catalogue, the database design, the API catalogue generated from endpoints.json, the design plan and screen inventory, the mobile guides for Imad's Flutter repo, the ways of working (Git flow, reviews, definition of done), and the scheduled plan (tasks.json → Gantt, milestones, generated team-task briefs). Out of scope: freezing module boundaries (SRV-01) and the executable contract (SRV-03). The cadrage workshop (PRJ-03) walks HOCO through this baseline.

Note

Delivered on 17 Oct 2026.

Subtasks

#SubtaskOwner
1Fumadocs site with MDX components (Mermaid, PlanSummary, Gantt, TaskTable, RequirementTable, ScreenTable, EndpointTable, EnumTable, RefScreen)Anis
2Canonical data files requirements.json, screens.json, endpoints.json, enums.json and their rendering componentsAnis
3PRD, user flows and SRS pages (requirements by area, lifecycles, business rules, permissions and notifications matrices, acceptance scenarios)Anis
4Architecture, service catalogue, database design and API catalogue pagesAnis
5Design plan, design-system brief and screen inventory for the four interfacesAkram
6Mobile guides (Flutter workspace, architecture, offline, integration, release) for hoco-mobileImad
7Plan: tasks.json with scheduler (Sunday–Thursday week, holidays), milestones, Gantt and generated team-task briefsAnis
8Docs site runnable locally; deployment on the VPS planned with OPS-02Anis

Deliverables

  • apps/docs/content/docs/{prd,user-flows,srs,design,mobile,workflow,architecture,timeline}
  • apps/docs/content/spec/{requirements,screens,endpoints,enums}.json and apps/docs/content/plan/tasks.json
  • Generated team-task pages under /docs/team-tasks/<person>/<task-id>
  • Docs site builds and runs locally (VPS deployment with OPS-02)

Acceptance criteria

  • The docs site builds without MDX errors and every page has a title and description
  • Every requirement, screen and endpoint id resolves to an anchor on its page
  • Dates on the timeline come only from the scheduler, never from hand-typed text
  • The 17 Oct 2026 product decisions (three customer-type prices, availability-only stock, guest mode, manual order confirmation, SSE for resellers, regional WhatsApp, V1 returns and SAV) are reflected in the SRS

Test measures

  • Docs build in CI (link and MDX checks)
  • Manual walk-through of the SRS by Imad and Akram before the cadrage workshop

KPI

  • Delivered by Sat 17 Oct 2026 within 1 person-day(s).
  • Every acceptance criterion above demonstrated before hand-off; linked requirements' acceptance criteria pass.
  • Zero open critical defects, permission gaps or data-integrity regressions at sign-off.

Generated from content/plan/tasks.json by scripts/generate-team-tasks.mjs. Dates are computed by the scheduler (Sunday–Thursday weeks, holidays excluded) — change the plan, not this page.

On this page