backend-design

To generate an OpenAPI spec from a PRD and data dictionary, translate product discovery artifacts into concrete backend specifications. This requires mapping PRD FR-IDs to API contracts, aligning schemas with the data dictionary, and defining explicit error handling.

Designing database schemas from product design artifacts involves mapping schema designs to database tables with migration plans. This process ensures backend specifications remain traceable to PRD requirements and aligned with the data dictionary.

Modeling auth and permissions for a new product backend requires translating discovery outputs into an integration-ready auth model. You must define explicit integration points and ensure traceability to PRD FR-IDs during the API contract design phase.

Yes, API contract design requires strict traceability to PRD FR-IDs. Translating product discovery into backend specifications ensures APIs, schemas, and auth models remain verifiable against functional requirements and aligned with the data dictionary.

Handling pagination and error handling during OpenAPI spec generation requires explicitly defining these elements within the API contracts. You must translate discovery artifacts into backend specifications that include defined error handling and pagination for list endpoints.

You need backend specifications for new products during Phase 4 coordination, applying them to API contract design, OpenAPI spec generation, database schema design, and auth modeling. This ensures implementation-ready handoff from product discovery outputs.