PRDs & use cases

Product requirement documents written for alignment and velocity — problem framing, user flows, acceptance criteria, and technical constraints in one place.

How I write specs

  • Problem statement with success metrics and explicit non-goals
  • User stories, edge cases, and API or integration requirements
  • Phased rollout with acceptance criteria per milestone
  • Dependencies, risks, and open questions flagged upfront
← Back home