sc4sap:deep-interview

Clarify vague SAP requirements through structured Socratic interviews before coding.

46|15|Updated Apr 13, 2026

Search Tags:#specification #requirements #ambiguity #interview #gating #sap #badi

Ready to run

npx skills add https://github.com/babamba2/superclaude-for-sap --skill sc4sap-deep-interview

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: sc4sap:deep-interview
Source: https://github.com/babamba2/superclaude-for-sap/tree/main/skills/deep-interview
Command: npx skills add https://github.com/babamba2/superclaude-for-sap --skill sc4sap-deep-interview

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

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.

Core Features & Use Cases

Resolves ambiguity across SAP object types (class, interface, program, function module, BAdI implementation, CDS view, RAP) through targeted questions.
Ambiguity gating with a scoring threshold: only when the ambiguity score falls below 5 is a spec generated and progression offered.
Writes validated spec to .sc4sap/deep-interviews/sap-{timestamp}.md and prompts to proceed to /sc4sap:create-program or /sc4sap:create-object.

Quick Start

Say "deep interview" with your vague SAP requirements to begin structured questioning.

Frequently Asked Questions about sc4sap:deep-interview

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I clarify vague SAP requirements before writing ABAP code?▼

To clarify vague SAP requirements before writing ABAP code, you can use a structured Socratic interview to resolve ambiguity across SAP object types like classes, programs, and CDS views. This prevents wasted execution cycles on underspecified tasks.

When do I need a structured interview for SAP development tasks?▼

You need a structured interview for SAP development tasks when requirements are vague or complex and you require guided questioning to specify SAP object types, packages, transports, and integration points before implementation begins.

How does the ambiguity scoring mechanism work for SAP specifications?▼

An ambiguity gating mechanism scores requirements during the interview process. Only when the ambiguity score falls below 5 is a validated spec generated, ensuring your SAP development requirements are fully crystallized before progression.

Can I specify BAdI implementations and RAP objects through guided questioning?▼

Yes, you can specify BAdI implementations and RAP objects through guided questioning. The interview resolves ambiguity across various SAP object types, including classes, interfaces, function modules, CDS views, and RESTful ABAP Programming objects.

What happens after the SAP requirements interview is completed?▼

After the SAP requirements interview is completed, validated specifications are written to a markdown file. The system then prompts you to proceed directly to creating programs or objects, transitioning smoothly from specification to code generation.

What is the best way to document validated SAP specifications?▼

The best way to document validated SAP specifications is writing them to a timestamped markdown file in the deep-interviews directory. This ensures requirements are permanently recorded and accessible before you proceed to code creation.