Building Project Requirements With Ai

## 🌱 How to Complete This Project: Step-by-Step

Follow these steps to build your AI-assisted product requirements:

1. - [ ] Refresh Key Concepts (5 mins)

Before diving in, quickly revisit these sections in the main lesson: * "Things to Avoid When Building Product Requirements with AI" * "Understanding the Minimum Viable Product" This will set the right mindset!

2. - [ ] Complete Your MVP Product Planner (15-20 mins)

This planner is your first crucial step. Grab a pen or open a text editor and fill this out for your project idea:

---

MVP Product Planner

Purpose: Design the simplest version of a product that solves a user's problem Time: 15-20 minutes Instructions: Answer each question to create a clear plan for your MVP. Keep it simple—focus on the user's core need!

1. Problem 🎯 What problem does your product solve? Who faces it? (Write 1 sentence about the problem and the user.)

---

2. Core Benefit 💡 What's the one key thing your product does to fix the problem? (Write 1 sentence describing the main benefit.)

---

3. Core Features ⚙️ List exactly 3 must-have features to deliver the benefit. (Cross out anything "nice-to-have.")

1. ---

2. ---

3. ---

4. User Flow 🛤️ Write 3-5 steps showing how the user uses your product. (Keep it simple, like a straight line from start to finish.)

1. ---

2. ---

3. ---

5. Success 🏆 How will you know if your product works for users? (Write 1 measurable goal e.g., time, satisfaction.)

---

💡 Pro Tips from the lesson:

• Focus on one user goal.
• If a feature feels complex, save it for later.
• Think: "What's the least I need to build to help the user?"

---

3. - [ ] Generate MVP Requirements with AI (10 mins)

Now, let's use the AI to draft your requirements. Copy the prompt below, replace the placeholders with your answers from the MVP Product Planner you just filled out, and run it in your AI tool.

1Act as an expert product manager and create a Minimum Viable Product (MVP) requirements document based on the provided input, following the MVP Product Planner structure. The goal is to design the simplest version of a product that solves a specific user problem, focusing on core features and avoiding feature creep, overspecification, or unnecessary complexity. Use the following input to fill out the planner and propose minimal, effective features and a user flow. Suggest technologies only if necessary, prioritizing simplicity and flexibility, and avoid imposing hallucinated constraints or overly detailed requirements. Ensure the output is clear, concise, and actionable, with a measurable success metric.
2
3**Input**:
4- Problem: [Insert YOUR answer from Planner Section 1]
5- Core Benefit: [Insert YOUR answer from Planner Section 2]
6
7**Instructions**:
81. **Problem**: Restate the problem and user from the input.
92. **Core Benefit**: Restate the core benefit from the input.
103. **Core Features**: Propose exactly 3 must-have features to deliver the core benefit. Exclude 'nice-to-have' features like advanced designs or complex functionalities. Ensure features are simple and aligned with the MVP methodology.
114. **User Flow**: Outline 3-5 simple steps showing how the user interacts with the product to achieve the core benefit. Keep it linear and minimal.
125. **Success**: Define 1 measurable goal to evaluate if the product solves the problem (e.g., time saved, user satisfaction).
136. **Optional**: If relevant, suggest 1-2 technologies or tools for implementation, but only if they enhance simplicity or speed of development. Avoid heavy opinions on tech stacks.
14
15**Output Format**:
16Use the MVP Product Planner structure:
17- Problem: [Restated problem]
18- Core Benefit: [Restated benefit]
19- Core Features:
20  1. [Feature 1]
21  2. [Feature 2]
22  3. [Feature 3]
23- User Flow:
24  1. [Step 1]
25  2. [Step 2]
26  3. [Step 3]
27- Success: [Measurable goal]
28- [Optional] Suggested Technologies: [1-2 simple tools, if applicable]
29
30**Constraints**:
31- Stick to the MVP methodology: focus on the minimum needed to validate the product.
32- Avoid feature creep, overspecification, or imaginary technical limitations.
33- Keep the response concise (under 300 words).
34- If the input is incomplete, make reasonable assumptions based on the problem provided and note them.

4. - [ ] Review and Refine Your AI-Generated Requirements (10-15 mins)

Critical thinking time! Look at what the AI generated: * Is it clear and concise? * Does it truly stick to the MVP scope you defined in your planner? * Are there any "hallucinated constraints" or features that seem overly complex for an MVP? * Edit the AI's output until you're happy it represents a lean, focused MVP.

5. - [ ] (Optional but Highly Recommended) Quick User Validation

Got your refined MVP concept? Great! * Briefly explain the problem and your 3 core features to 1-2 potential users. * Does it resonate? Do they understand the benefit? * Even a 5-minute chat can provide amazing insights. Don't skip this if you can!