ביתלמידהקורסיםוובינרים
PM × AIבוחר לך את הצפייה הבאה
למידהקורסיםשירותיםוובינרים
EN
PM × AI

בהנחיית עופר רגב — מנהל מוצר שמשחרר מוצרים עם AI.

הצטרפו לקבוצת הוואטסאפ
  • LinkedIn
  • YouTube
  • GitHub
  • theaipmhub@gmail.com
לעבוד איתי
  • קורסים חיים
  • סדנאות לצוותים
  • ייעוץ
  • קורס AI למנהלי מוצר
תוכן חינמי
  • מפת הלמידה
  • מאמרים
  • סרטונים
  • סקילז
  • וובינרים
  • קבוצת וואטסאפ
© 2026 The AI PM Hub · נבנה למנהלי מוצר
אודותצור קשרתנאי שימושפרטיותנגישות
  • המפה
  • מאמרים
  • סרטונים
  • סקילז
  • אני חדש ב-AI. מאיפה מתחילים?
  • יש לי רעיון למוצר. איך מגיעים ל-MVP?
  • איך עובדים עם Claude ו-Claude Code?
  • אני מחפש עבודה או מתכונן לראיונות.
  • Rules, Commands או Skills? המדריך של מנהל מוצר לבחירה הנכונה
  • להפסיק לשלוח את אותם קורות חיים: מערכת חיפוש עבודה בשמונה שלבים שאפשר להריץ עם Claude
  • בניתם אב-טיפוס. הנה מה שמפריד בינו לבין אפליקציה אמיתית
למידה

סקילז

רוב התוכן כתוב באנגלית.

← חזרה למפה

כל התוכן

הכולמאמריםסרטוניםסקילז
נושאיםAI BasicsAI for PMsCareerClaudeClaude Co-work
Claude Co-Work
Claude Code
Claude Skills
Discovery to MVP
Git
Idea to MVP
Job Hunter
Prioritization
Product Builder
Product Discovery
Product Management
Product Sense
Roadmap
Skills
Vibe Coding
Webinar
Webinar recording
32 תוצאותהחדשיםא–ת
  • סקילidea-to-mvpUse when a product manager has a product idea and wants to turn it into an MVP requirements doc — e.g. "I have an idea for…", "help me scope/spec an MVP", "write a PRD for…", "validate this product idea" — or wants to resume a flow (a product/<slug>/00-status.md exists in the workspace).
  • סקילpm-intakeUse when a product manager starts exploring a new product idea that hasn't been scoped yet (no product/<slug>/ folder exists for it), or asks to kick off idea discovery. Step 1 of the idea-to-mvp flow.
  • סקילpm-usersUse when identifying who a product idea is for — user segments, users vs. paying customers, target audience, "who is this for" — or when 01-intake.md exists but users haven't been defined. Step 2 of the idea-to-mvp flow.
  • סקילpm-use-casesUse when defining what target users are trying to accomplish and where it hurts today — use cases, jobs, pain points — before any feature discussion, or when 02-users.md exists but use cases don't. Step 3 of the idea-to-mvp flow.
  • סקילpm-alternativesUse when assessing how target users solve their problem today — competitors, substitutes, manual workarounds — and where those fall short, or when 03-use-cases.md exists and current-market context is needed. Step 4 of the idea-to-mvp flow.
  • סקילpm-solutionsUse when generating and comparing multiple solution directions for validated use cases before committing to one — solution brainstorm, concept exploration — or when use cases exist but no solution has been chosen. Step 5 of the idea-to-mvp flow.
  • סקילpm-mvp-cutUse when deciding what is in and out of an MVP — prioritizing a feature list into must/later/won't, scoping v1, "what's the smallest version" — or when a solution direction exists but scope is undefined. Step 6 of the idea-to-mvp flow.
  • סקילpm-validationUse when defining how to know an MVP worked — success metrics, north star, riskiest assumptions, kill criteria, validation plan — or when MVP scope exists but success is undefined. Step 7 of the idea-to-mvp flow.
  • סקילpm-prdUse when assembling a final lean PRD / MVP requirements doc from completed discovery docs, or when a PM asks to "write the PRD" after idea-to-mvp steps (product/<slug>/ docs 01–07 exist, fully or partly). Step 8 of the idea-to-mvp flow — core steps end here; an optional Lean PMF search (steps 9–11) can follow.
  • סקילpm-lean-canvasUse when mapping out the full business model — channels, revenue, cost, key metrics, unfair advantage — for an idea, or when 08-prd.md exists but no lean canvas yet. Step 9 of the idea-to-mvp flow (Lean PMF search).
  • סקילpm-customer-discoveryUse when designing customer discovery interviews to test problem/customer assumptions, or synthesizing findings from interviews already run, or when 09-lean-canvas.md exists but discovery hasn't started. Step 10 of the idea-to-mvp flow (Lean PMF search).
  • סקילpm-pmf-signalUse when defining how you'll know product-market fit has been reached — PMF survey, retention target, go/no-go threshold — or when 10-customer-discovery.md exists but no PMF signal plan yet. Step 11, final, of the idea-to-mvp flow (Lean PMF search).
  • סקילroadmap-prioritizerTurns an existing codebase into a prioritized roadmap. Reads the project's code and docs to establish a status per feature (shipped, in progress, planned), generates fresh opportunity ideas the code only hints at, gets the user's sign-off on the combined list, then recommends which prioritization model actually fits this situation — RICE, MoSCoW, Now/Next/Later, or Kano — instead of defaulting to one. Runs the chosen model as an interactive conversation in plain language (no jargon or spreadsheets required from the user) and writes a roadmap doc with status and priority per feature, rationale, and a dependency-aware build order.
  • סקילdiscovery-to-mvpTakes the PM through the discovery pipeline one step at a time, from raw customer interview transcripts to a scoped v1, a prototype brief, a built prototype and an honest critique, showing the results of each step and stopping for the PM's decision before the next.
  • סקילinterview-guideWrites a discovery interview guide before customer or stakeholder calls — learning goals, the riskiest assumption behind each, and event-anchored questions per persona, plus recording setup that makes later synthesis reliable.
  • סקילtranscript-reconcileCleans and merges one or two auto-generated transcripts of the same call into a single trustworthy transcript with correct speaker attribution, glossary fixes, numbered turn IDs and a log of every judgment call. Use before any interview synthesis, when transcripts come from Zoom, Meet, Otter, Granola or similar, when speaker labels look wrong, when two transcripts of one call disagree, or when a transcript needs translating.
  • סקילpersona-extractPulls one persona's evidence out of a merged interview transcript — pains with verbatim quotes and severity, workarounds, numbers, prompted vs unprompted signals, stated vs revealed gaps, what must not change, and conspicuous silences — every line tied to a turn ID. Use after transcripts are cleaned, when someone asks what a customer or stakeholder "really said", or before comparing personas.
  • סקילpersona-collideCompares two or more persona extracts to find where people want opposite things, tell different stories about the same event, or both assume someone else owns a step — including a workflow map with an owner for every step and a list of what nobody mentioned.
  • סקילproblem-framingTurns discovery evidence into a solution-free problem statement under 80 words, compares it with how the original brief framed the problem, offers rejected alternative framings with reasons, and defines what "solved" would look like per persona. Use after synthesizing interviews and before scoping, or when someone asks "what problem are we actually solving" or suspects the brief asked for the wrong thing.
  • סקילmvp-scope-cutlistScopes a v1 from a framed problem and discovery evidence — what v1 does, what it explicitly doesn't, a cut list where every cut has a reason, a cost and a revisit trigger, and an adoption plan for getting busy users off their current channel. Invites and handles the PM's pushback.
  • סקילprototype-briefRanks a v1's assumptions by risk and testability, picks the single riskiest one a prototype can test, and writes a build-ready prototype brief — one flow, realistic mock data drawn from the interviews, what's real vs faked, success criteria, a user test script and a paste-ready build prompt. Use after scoping and before building, or when someone asks "what should we prototype first".
  • סקילprototype-build-critiqueBuilds the single-flow prototype described in a prototype brief and then critiques the proposal and prototype as a skeptical head of product — is the "why" clear for the customer and the business, does the prototype test the assumption, which sentences sound AI-written, and what to cut.
  • סקילapplication-packagerBuilds a complete job application package in one guided conversation: company research, fit analysis, tailored CV, cover letter, and stage prep doc.
  • סקילnotion-connectorSets up or locates a job-search tracker structure — three trackers for applications, target companies, and networking contacts — either in the user's Notion workspace or as local files on their machine.
  • סקילtarget-company-finderResearches and maintains a ranked list of target companies in the user's job tracker (Notion or local files).
  • סקילcompany-researcherConducts deep company research for job seekers preparing for applications or interviews.
  • סקילfit-analyzerProvides an honest fit assessment between a candidate's CV and a job description.
  • סקילcv-builderConducts a friendly conversational interview to build a complete ATS-optimized CV from scratch.
  • סקילcv-tailorTailors and rewrites a candidate's CV for a specific job role, reordering and reframing content to surface JD keywords without inventing anything.
  • סקילcover-letter-writerWrites a targeted, specific cover letter for a job application using company research and fit analysis.
  • סקילinterview-prepCreates stage-specific interview preparation documents for job seekers at any stage of the hiring process.
  • סקילproduct-sense-interviewInteractive product-sense / product-design PM interview coach built strictly on the frameworks in "Cracking the PM Interview" (McDowell & Bavaro).