Feature Spec Generation

## What You'll Learn - What a feature spec is (and why founders need them) - The difference between PRDs, specs, and user stories - The Feature Spec Prompt Template (exact format) - What to include: Problem, solution, user flow, edge cases, metrics - How to hand off specs to developers - Real examples: Login flow, payment integration, search feature --- ## Why This Matters (3 min read) **The Scenario:** **Founder:** "We need a login feature." **Developer:** "Sure. What kind of login?" **Founder:** "Um... the normal kind? Email and password?" **Developer:** "Got it. Should users verify their email? What about password reset? Social login? Two-factor auth? Session timeout? What happens if they enter the wrong password 5 times?" **Founder:** *[Head spinning]* "I... I don't know. Just make it work like other apps?" **Developer:** *[Frustrated]* "Which apps? They all work differently." --- **What Went Wrong:** The founder thought "login feature" was self-explanatory. The developer needed 20+ decisions answered: - Email verification? (Yes/No) - Password requirements? (Min length, special chars?) - Social login? (Google, GitHub, both, neither?) - Password reset flow? (Email link? Security questions?) - Failed login attempts? (Lock after 5 tries? Show CAPTCHA?) - Session duration? (Stay logged in forever?...