From PRD to Prompt
As a PM, you already know how to write requirements. The key insight is that a good prompt IS a mini-PRD. The same skills that make you good at product specifications make you good at vibe coding.
The Anatomy of a Great Prompt
1. Context (The "Why")
Set the stage. What's the project? What exists already?
"I'm building a task management app for a small team. We already have a basic list view working."
2. Objective (The "What")
What specific thing do you want to build or change?
"Add a feature to mark tasks as complete with a checkbox."
3. Requirements (The "How")
Specific behaviors and constraints.
"When clicked, the checkbox should toggle. Completed tasks should have strikethrough text."
💡 Pro Tip
When stuck, ask Claude to help: "I want to add X feature but I'm not sure how to specify it. Can you ask me clarifying questions?"