Skip to main content

Standing Product Requirements (managed)

A governed, managed list of product requirements that apply to every feature by default. The product→R&D handoff tooling (bewith-product-handoff) reads this file live and merges each entry into PRD section 8.2 (API-First / API-accessible capabilities) automatically — even when the author did not restate it. The author defines these once here; they flow into every handoff without repetition.

Rules​

  • Each entry is a WHAT/WHY capability, never HOW β€” no endpoints, schemas, routes, or architecture.
  • The handoff merges these into Β§8.2 of every generated PRD. If this file is absent, the tooling proceeds and notes that standing requirements were not applied.
  • This list is governed: changes are approved by Product + CTO (a deliberate, managed list β€” not ad-hoc per feature). It is the BACK/contract half; the product plugin only reads it.

Standing requirements​

SR-1 β€” Headless / API-first​

Every feature must be programmatically reachable (headless), so customers can consume our products as a headless system. The capability β€” not its routes β€” belongs in Β§8.2 of every PRD. Why: the product is sold/consumed as a platform; UI-only business logic is not acceptable.