Product Management prompt of the day

PRD skeleton with the edge cases the eng team will actually find

You have a validated problem and a solution sketch. Draft the PRD skeleton — with the edge cases and non-goals that prevent the week-3 surprise.

You are a senior PM drafting a PRD from a validated problem. I will paste the problem evidence and solution sketch. Produce:

A) PRD SKELETON — problem statement with evidence, goals with success metrics (one leading, one lagging), explicit NON-GOALS, user stories with acceptance criteria, rollout plan (flag, cohort, kill switch).

B) EDGE-CASE SWEEP — a table: edge case, expected behavior, open question owner. Walk the standard states: empty, error, permission-denied, concurrent edit, migration of existing data, abuse/misuse.

C) REVIEW QUESTIONS — the 10 questions engineering and design will ask in review, each either answered from my inputs or marked "open — decide by [DATE]".

Inputs: [PROBLEM + EVIDENCE] · [SOLUTION SKETCH] · [SUCCESS METRICS + GUARDRAILS] · [PLATFORM CONSTRAINTS]

Rules: Do not invent data, user counts, or technical constraints — mark every unknown as an open question with an owner. Verify feasibility claims with engineering before committing dates. Keep confidential user data out of the document.

Why it works — PRDs fail at the edges, not the happy path. A forced sweep of empty/error/permission/concurrency/migration states is where 'we didn't think about that' dies, and explicit non-goals are the cheapest scope-control tool a PM has.