Skill

sc4sap:deep-interview

Conducts Socratic interview to clarify vague SAP/ABAP requirements on objects, packages, transports, patterns, integrations, data models, and testing before generating validated specs.

backend

npx claudepluginhub babamba2/superclaude-for-sap --plugin sc4sap

Configuration

Model: haiku

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Follows OMC `deep-interview` pattern adapted for SAP. Conducts a structured Socratic interview to crystallize SAP development requirements before any code is written. Prevents wasted execution cycles on underspecified ABAP tasks.

SKILL.md

Similar Skills

sc4sap:create-program

Creates ABAP programs (Report/CRUD/ALV/Batch) with Main+Include structure, OOP or procedural paradigms, and full agent-driven coding/QA pipeline. For new executable REPORTs from scratch.

13 files

sc4sap

sap-abap

182

Assists with ABAP code for SAP systems: internal tables, structures, ABAP SQL, OOP, RAP, CDS views, EML statements, ABAP Cloud, strings, dynamic programming, RTTI/RTTC, field symbols, data references, exceptions, unit testing.

20 files

sap-abap

interview

3.4k

Conducts Socratic interviews to crystallize vague requirements into clear specifications. Triggers on 'interview me' or 'clarify requirements'; invoke via /ouroboros:interview [topic].

ouroboros

Stats

Stars22

Forks8

Last CommitApr 23, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

SC4SAP Deep Interview

Follows OMC deep-interview pattern adapted for SAP. Conducts a structured Socratic interview to crystallize SAP development requirements before any code is written. Prevents wasted execution cycles on underspecified ABAP tasks.

sc4sap:deep-interview asks targeted questions to resolve ambiguity in SAP requirements. It gates on a mathematical ambiguity threshold: only when requirements are sufficiently specified does it produce a validated spec file and offer to proceed to `/sc4sap:create-program` or `/sc4sap:create-object`.

<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>

<Use_When>

Requirement is vague (no object names, package, transport, or system details)
User says "deep interview", "ask me questions", "help me spec this", or "I'm not sure what I need"
Task involves complex SAP scenarios (RAP, BAdI, enhancement framework) where wrong assumptions are costly
User is unfamiliar with SAP object types and needs guidance on the right approach </Use_When>

<Do_Not_Use_When>

Requirements are concrete (specific class name, method signature, package) -- proceed directly to /sc4sap:create-object
User wants immediate execution on a full program spec -- use /sc4sap:create-program
Task is a one-line fix -- skip interview entirely </Do_Not_Use_When>

<SAP_Interview_Dimensions> The interview covers these dimensions until each is resolved:

Object scope: What ABAP objects are needed? (class, interface, program, function module, BAdI implementation, CDS view, RAP business object)

Package and transport: Which development package? New transport or existing? Which system landscape (DEV -> QAS -> PRD)?

Technical pattern: OO class hierarchy? Procedural? RAP/OData? Enhancement spot/BAdI? Which release (ECC vs S/4HANA)?

Integration points: Which SAP modules does this touch? (FI, MM, SD, HCM, etc.) Any BAPIs, RFCs, or IDocs involved?

Data model: Which tables are read/written? Custom Z-tables or standard SAP tables? Authorization objects needed?

Testing requirements: Unit tests needed? Which test classes? Test data strategy? </SAP_Interview_Dimensions>

<Ambiguity_Gating> After each round of questions, score ambiguity 0-10:

8+: too vague, continue interview
5-7: borderline, ask 1-2 clarifying questions
Below 5: sufficient, generate spec

Do not proceed to spec generation until score is below 5. </Ambiguity_Gating>

When ambiguity threshold is met: 1. Write validated spec to `.sc4sap/deep-interviews/sap-{timestamp}.md` 2. Spec includes: object list, package, transport strategy, technical pattern, integration points, test requirements 3. Offer: "Spec ready. Proceed with `/sc4sap:create-program` (full program) or `/sc4sap:create-object` (single object)?"

Task: {{ARGUMENTS}}