From sc4sap
Conducts a Socratic interview to crystallize ambiguous SAP/ABAP requirements before generating code. Gates on ambiguity threshold and produces a validated spec file.
How this skill is triggered — by the user, by Claude, or both
Slash command
/sc4sap:deep-interviewhaikuThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
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.
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.
<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>
<Do_Not_Use_When>
/sc4sap:create-object/sc4sap:create-program<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:
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}}
npx claudepluginhub babamba2/superclaude-for-sap --plugin sc4sapCreates new ABAP programs (Report, CRUD, ALV, Batch) with Main+Include structure supporting OOP or Procedural paradigms using a multi-phase coding and QA pipeline.
Socratic interview to crystallize vague requirements into clear specifications before coding.
Conducts structured requirements-gathering interviews for software features/systems. Reads SPEC.md and context, asks numbered questions on purpose, technical design, UI/UX, edge cases, security, rollout. For deep requirement elicitation before specs/plans.