myb-p-fit-gaplisted

Run a Fit-Gap analysis for a MyBusiness CRM customer - classify every requirement from the discovery document against actual product capabilities and produce a branded Hebrew HTML report + machine-readable workbook. Use after business discovery (אפיון) when the user asks for - fit gap, ניתוח פערים, ניתוח התאמה, gap analysis, 'מה המערכת יודעת לעשות מתוך הדרישות', סיווג דרישות, scope decision, הערכת היקף לדרישות, או כשיש req-register.csv שצריך לסווג. Classification uses the evidence-backed capability matrix (never intuition), the ladder Native/Config/Custom-JS/Custom-Server/External/Gap plus Process-change and Defer dispositions, and produces effort + ownership per requirement. Input - the discovery REQ register; output feeds functional-spec.
AviMYB/mybusiness-plugins · ★ 2 · Data & Documents · score 63

Install: claude install-skill AviMYB/mybusiness-plugins

# Fit-Gap Analysis — ניתוח התאמה ופערים Classify every requirement to the **cheapest rung that genuinely works**, with evidence, and hand the customer a scope decision they can sign. Method: our capability ladder + the fit-to-standard-first principle (adopt > adapt > build), gap dispositions with written justification, and a traceable workbook the spec skill consumes. ## Knowledge sources (binding lookup order — never classify from memory) 1. **Capability matrix**: `../myb-p-kb/references/80-capability-matrix/01-capability-matrix.md` → then ALWAYS `02-known-limitations.md` before any "yes". The matrix is evidence-backed; if a row is missing, check `30-customization/12-solution-blueprints.md` (solved patterns: SLA, import, web2lead, multi-select, cascading, portals…), then the domain doc, then verify live on a sandbox before classifying. ⚠️ UNVERIFIED items must be verified before promising. 2. Effort anchors: `../myb-p-kb/references/60-implementation-methodology/06-estimation-guide.md`. 3. Method: `../myb-p-kb/references/60-implementation-methodology/03-fit-gap-analysis.md` + this skill's `references/classification-playbook.md`. **Precedence: the workbook/CSV header in this skill's `references/output-spec.md` §2 is the authoritative contract; the KB method doc (and any template CSV) is background — on any schema difference, output-spec wins.** 4. Effort anchors: `../myb-p-kb/references/60-implementation-methodology/06-estimation-guide.md`. ## Inputs - `req-register.csv`