Write a PRD

Turn a free-form description of a problem into a structured PRD file through codebase exploration and relentless user interview.

Process

1. Collect the plan

Ask the user for a long, detailed description of the problem they want to solve and any initial ideas for solutions. There is no required format — a brain dump is fine. The goal is to understand their thinking before touching the codebase.

Also ask for the file format and location where the PRD should be saved.

2. Explore the codebase

Before interviewing the user, explore the repo to verify their assertions and understand the current state of the implementation. Look for:

• Modules and files that will be affected by this change
• Existing patterns, conventions, and abstractions to follow or build on
• Anything that contradicts or complicates the user's description of the current state