sc4sap:compare-programs

SC4SAP Compare Programs

Reads 2–5 ABAP programs that implement the same business scenario but in different variants, analyzes them across 10 business dimensions, and emits a side-by-side Markdown comparison targeted at functional consultants (not developers).

This skill crystallizes why each variant exists so a consultant can:

• pick the right program for a new requirement instead of creating a 4th,
• map fit/gap across localizations,
• brief a handover or knowledge transfer without reading ABAP.

<Response_Prefix> Every response triggered by this skill MUST begin with [Model: <main-model> · Dispatched: <sub-summary>] per ../../common/model-routing-rule.md § Response Prefix Convention. </Response_Prefix>

<Phase_Banner> Multi-phase skill. Before each Agent(...) dispatch, emit ▶ phase=<id> (<label>) · agent=<name> · model=<Opus 4.7|Sonnet 4.6|Haiku 4.5> per ../../common/model-routing-rule.md § Phase Banner Convention. </Phase_Banner>

<Team_Mode> Step 4b is the integration point for Type A teamMode (Cross-Module Consultant Panel). When module_set ≥ 2 (existing Step 4b gate), Round 1 runs always — positions are parsed for ownership conflicts (same program claimed PRIMARY by 2+ modules). On conflict, escalate to Rounds 2-3 per team-mode.md. No conflict → positions pass directly to Step 5 writer render (legacy path). Base protocol: ../../common/team-consultation-protocol.md. </Team_Mode>

<Use_When>

• User says "compare programs", "what's the difference between A and B", "MM vs CO version", "country-specific programs", or equivalent in the user's language
• Consultant handover / AMS transition — need to document "when to use which"
• Fit/Gap analysis across country rollouts — same flow, different programs
• Rationalization / decommissioning — considering whether to merge duplicates </Use_When>

<Do_Not_Use_When>

• Only one program → use /sc4sap:program-to-spec instead
• User wants code quality review (not business intent) → /sc4sap:analyze-code
• User wants to build a new program → /sc4sap:create-program
• More than 5 programs — break into multiple comparison sessions </Do_Not_Use_When>

<Session_Trust_Bootstrap> MANDATORY — runs as Step 0 before any MCP call or user interaction.

Invoke /sc4sap:trust-session with parent_skill=sc4sap:compare-programs to pre-grant MCP tool + file-op permissions (eliminates per-tool prompts during parallel program reads).

• If .sc4sap/session-trust.log already has a line within the last 24h, skip silently.
• Otherwise run it and surface the one-line confirmation.

Full spec: see ../trust-session/SKILL.md. </Session_Trust_Bootstrap>

<Companion_Files> MANDATORY: Read the companion files below before executing. Each covers a self-contained section:

Companion	Scope
comparison-scope.md	10 business comparison dimensions + default scope + scope-selection prompt template
workflow.md	6-step execution flow (Input → Scope → Facts × N → Analyze → Render → Follow-up)
dispatch-prompts.md	Full Agent(...) prompt bodies for Steps 3, 4, 4b, 5 (kept out of workflow.md to honor the 200-line cap)
report-template.md	Markdown report skeleton (Executive Summary → Matrix → Per-program detail → Recommendation)
</Companion_Files>

<Agent_Composition> Per-step model allocation. Skill frontmatter pins the main thread to Haiku; each Agent(...) carries its own model (frontmatter or explicit override).