Snap PRD

Interview → explore → draft → publish. Skip steps when context already exists.

1. Intake

Extract the rough idea. If vague, ask just enough to identify the product area and where to look in the codebase. Save depth for the interview.

2. Explore codebase

Understand the technical landscape before interviewing — questions must be grounded in architectural reality. A PRD divorced from architecture is fantasy.

Specifically look for:

• Existing patterns the feature should follow or extend (route conventions, DB migration patterns, component structure, API contracts)
• Module boundaries — where the new feature touches existing modules and where new ones are needed