efune

name	efune
description	Turn a messy client discovery-call transcript into a pre-filled, ready-to-send expectations-alignment questionnaire (שאלון תיאום ציפיות) for AI agent projects. Use when the user says "/efune", "create an efune for [client]", "תכין תיאום ציפיות", "turn this discovery call into a scoping form", or pastes a discovery transcript and asks to scope it.

Efune — Discovery Call → Scoping Questionnaire

You turn a raw discovery-call transcript (or call notes) into a polished, pre-filled Hebrew expectations-alignment questionnaire the builder sends to their client. The output is an HTML file based on template/efune-form-template.html in this skill's repo.

Core principle

Every field that CAN be pre-filled from the call MUST be pre-filled and tagged "מולא מראש". Only what is genuinely unknown stays tagged "להשלמה". A client who receives an empty form abandons it. A client who receives a form that already knows their business corrects and completes it in 10 minutes.

Inputs

1. The transcript or notes of the discovery call (required). Accept pasted text, a file path, or a meeting-transcript MCP reference.
2. Builder config (ask once, remember for the session):
   • Builder name(s) as they should appear on the form (e.g. "יובל & איתמר")
   • Delivery window for a first agent (e.g. "בין שבעה לתשעה ימי עסקים. סוכן אחד, מחלקה אחת, מספר use cases מצומצם.")
   • Pricing orders of magnitude, one paragraph (e.g. "כ-X אלף ש״ח לסוכן לאופרציה ספציפית, עד עשרות אלפים לפעולות מורכבות. מתחילים מאפיון בתשלום, ומפרקים ל-Milestones שכל אחד מספק ערך בפני עצמו.")
   • Submission endpoint (Vercel /api/submit, Formspree URL, or webhook). If none: leave the default and note it in the handoff.

Extraction pass (do this BEFORE touching the template)

Read the full transcript and extract:

What	Goes to	Notes
Company name, industry, headcount, team structure	Part א	Quote numbers the client actually said. If two numbers conflict (e.g. website vs call), use the call's and flag the conflict to the builder
Decision-maker (who signs budget) + department leads	Part א	Titles matter: mark the מנכ"ל/owner explicitly
Every system mentioned (CRM, Slack, WhatsApp, email, ERP, project tool, site platform…) + what it's used for THERE	Part ב	One .sys row per system. The "what it's used for" line must come from the call, not from generic knowledge
Every pain, complaint, manual process, "falls between the chairs" moment	Part ד use cases	Convert each to a one-line use case. If the client themselves proposed it, append "(העלה <שם>)"
Constraints: channel boundaries ("my team won't move to WhatsApp"), security/privacy concerns, budget signals	Part ד scoping + handoff notes	Constraints shape which use case you recommend first
Timeline signals and who owes what next	"מה קורה אחרי" deadline	e.g. "עד שלישי או רביעי הקרוב"

Recommendation logic

Pick ONE recommended first use case (reco:true + the strip line). Criteria, in order:

1. The client proposed or reacted most strongly to it
2. One department, one channel, bounded scope
3. Human-in-the-loop, no production writes
4. Value visible within days of shipping

Never recommend the org-wide/orchestration vision as the first step — list it last as "החזון לטווח".

Build pass

1. Copy template/efune-form-template.html to <client-slug>-efune.html.
2. Replace every {{PLACEHOLDER}} (they are all documented in the template's header comment).
3. {{SYSTEMS_ROWS}}: one .sys block per extracted system, name="sys_<slug>" unique per row.
4. {{USE_CASES_JS}}: numbered array, recommended one first with reco:true, long-term vision last.
5. Keep ALL fixed copy verbatim — the three pain questions in Part ג, the "מה זה המסמך" callout, Part ו reassurance cards, and the closing line "הכול פתוח להתפלפלות משותפת". These are load-bearing; do not rephrase.
6. Hebrew style: no em dashes, no hyphens in number prefixes (write ב2024 not ב-2024). Latin tech terms keep their standard Hebrew-Latin hyphen (ב-Slack).

Output contract

Deliver to the builder:

1. The HTML file path
2. A 3-line deploy hint: vercel --prod (or any static host), form POSTs JSON to ENDPOINT — wire it to Formspree/Airtable/webhook, or swap for a mailto fallback
3. A short Hebrew message they can send the client with the link ("בהמשך לשיחה, הכנו לכם שאלון קצר...")
4. Flags: any conflicting facts from the call, any constraint that should shape the quote, and what the builder still owes the client

What this is NOT

• Not the full אפיון — the form says so explicitly, keep it that way
• Not a generic questionnaire — if fewer than half the fields are pre-filled, you did not read the transcript hard enough. Go back
• Never invent facts the call did not contain. Unknown = "להשלמה", not a guess