Stats
Actions
Tags
From sc4sap
Reverse-engineers ABAP programs into Functional/Technical Specification artifacts in Markdown or Excel. Uses Socratic narrowing to scope output to user needs.
How this skill is triggered — by the user, by Claude, or both
Slash command
/sc4sap:program-to-specsonnetThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Reads an existing ABAP program (Report / Module Pool / FM Group / Class / CDS / RAP) via MCP, runs structural + semantic + where-used analysis, then produces a Specification artifact in **Markdown** (`.md`) or **Excel** (`.xlsx`) format. Scope is **negotiated Socratically** — start wide, narrow on each turn, stop when the user's target granularity is confirmed.
Reads an existing ABAP program (Report / Module Pool / FM Group / Class / CDS / RAP) via MCP, runs structural + semantic + where-used analysis, then produces a Specification artifact in Markdown (.md) or Excel (.xlsx) format. Scope is negotiated Socratically — start wide, narrow on each turn, stop when the user's target granularity is confirmed.
<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>No teamMode integration. program-to-spec targets a single object (one program / class / FM group / CDS / RAP BO) and performs read-only structural extraction — no cross-module synthesis, no authoring conflict, no incident triage. See ../../docs/team-consultation-architecture.md § 6 gating logic. Future extension: if a target's GetWhereUsed graph spans ≥ 2 modules AND user picks L4 depth, Type A (module consultants annotating cross-module concerns in Step 3) could be added — not in current scope.</Team_Mode>
<Use_When>
<Do_Not_Use_When>
/sc4sap:analyze-code/sc4sap:create-programUpdate* calls or re-run /sc4sap:create-program<Session_Trust_Bootstrap> MANDATORY — runs as Step 0a before any MCP call or user interaction.
Invoke /sc4sap:trust-session with parent_skill=sc4sap:program-to-spec to pre-grant MCP tool + file-op permissions (eliminates per-tool prompts during structural reads + screen rendering pipeline).
.sc4sap/session-trust.log already has a line within the last 24h, skip silently.Agent dispatches within this skill MUST pass mode: "dontAsk".Full spec: see ../trust-session/SKILL.md.
</Session_Trust_Bootstrap>
<Socratic_Scope_Narrowing> The interview is a funnel: every turn reduces the remaining decision space. Score remaining ambiguity 0–10 after each answer; stop when ≤3.
Default opener — bundled 4-question AskUserQuestion (MANDATORY when the target object is already supplied in ARGUMENTS):
Issue ONE AskUserQuestion call with these four questions in this exact order — Audience / Format / Depth / Language — each a single-select with "(Recommended)" as the first option. This replaces Rounds 2+3+5 in one UI turn. Only fall back to per-round questioning when the object itself is missing or ambiguous (Round 1) or when the user picks L3/L4 (Round 4 scope trimming).
| # | Header | Question | Options (Recommended first) |
|---|---|---|---|
| 1 | Audience | Who is the primary audience for the spec? | Both (Recommended) · Functional · Technical |
| 2 | Format | Which output format? | Markdown (Recommended) · Excel · Both |
| 3 | Depth | What depth of detail? | L2 Standard (Recommended) · L1 Quick Spec · L3 Deep Technical · L4 Audit-grade |
| 4 | Language | Output language? | Korean · English · Japanese (order follows user's current language — promote the matching one to first with "(Recommended)") |
Round 1 — Target object (only if ARGUMENTS did not supply it)
SearchObject. If ambiguous, list candidates.Round 2 — Audience + format (covered by the default opener — do not ask separately)
Round 3 — Depth (pick one) (covered by the default opener)
| Depth | Contains |
|---|---|
| L1 — Quick Spec | Purpose, inputs, outputs, main logic steps (numbered; for Module Pool includes PBO/PAI module flow) |
| L2 — Standard Spec (default) | L1 + inputs & screens, data model, authorizations, outputs, exceptions, every subroutine / method signature |
| L3 — Deep Technical | L2 + SQL inventory, BAdI / exit list, performance notes |
| L4 — Audit-grade | L3 + line-level cross-references, where-used (scope: main object + screens × Z* / Y* callers), risk register, transport history |
Round 4 — Scope trimming (only if L3/L4) Ask ONE narrowing question per turn until ambiguity ≤3:
Where-Used scope (L4 only — fixed default, no interactive prompt)
Z* / Y* only (S2). Standard SAP and add-on namespaces are excluded.Where-Used section MUST repeat this scope in its header so reviewers know what was (and wasn't) searched.Round 5 — Output location
.sc4sap/specs/{object_name}-{YYYYMMDD}-{lang}.{md|xlsx}Stop condition: every dimension above has a concrete answer OR user explicitly says "skip remaining, use defaults". </Socratic_Scope_Narrowing>
<Workflow_Steps> The 6-step workflow (Step 0 Socratic → Step 5 Review) lives in a companion file to keep this skill doc short.
MUST read workflow-steps.md (in this skill folder) and execute the steps defined there in order whenever this skill runs.
</Workflow_Steps>
<Spec_Templates> The Markdown L2 skeleton and the Excel sheet-naming convention live in a companion file.
MUST read spec-templates.md (in this skill folder) when rendering the artifact in Step 4.
</Spec_Templates>
<Agent_Composition>
Per-step model allocation. Skill frontmatter pins the main thread to Sonnet; each Agent(...) carries its own model (frontmatter or explicit override).
sap-analyst × 1, Opus 4.7, frontmatter) — Step 3 primary dispatch: extracts business purpose, inputs, outputs, data sources (including CBO-annotated Z-references when cbo-context.md exists), main-logic narrative, authorization checks, error cases. One dispatch covers all narrative dimensions to keep context continuous.sap-writer × 1) — Step 3 second dispatch (or Step 4 render invocation):
model: "sonnet") — longer narrative + deeper cross-reference + stronger consistency requirement.scripts/spec/build-spec.mjs:
English source string → target-language replacement mapping; schema + slot semantics in spec-templates.md § Excel — Template-clone.{selection, alv, processFlow, lang} per-program image data; exact key names + sample values in spec-templates.md § Image Replacement. Drives the Sheet 3 Selection/ALV mockups + Sheet 4 horizontal Process Flow PNG.
Writer does NOT generate workbook styles, drivers, geometry, or PNGs directly — asset/template_base.xlsx supplies geometry, build-spec.mjs does clone + render + swap in one shot. Depth-driven model override still applies (Sonnet for L3/L4 because the warning-row and processing-step narrative is longer).sap-critic × 1, Opus 4.7, frontmatter, conditional L4 only) — Step 3 gate: verifies every claim in the rendered spec cross-references a concrete line range in source. Skip for L1 / L2 / L3.All Agent dispatches pass mode: "dontAsk" (trust-session granted in Step 0a).
</Agent_Composition>
<Output_Format>
Spec generated: ZSDR_OPEN_ORDER_ALV
Depth: L2 Standard · Format: markdown · Lang: ko
Sections: 9 · Tables referenced: 6 · Screens: 1 · GUI status: 1
File: .sc4sap/specs/ZSDR_OPEN_ORDER_ALV-20260414-ko.md
Top-level summary:
Report that lists open sales orders by Sales Organization and date range and displays them via ALV.
Main tables: VBAK, VBAP, VBUK, KNA1 (+ CDS I_SalesOrder).
Authorizations: S_TCODE=ZSDR01, S_TABU_DIS=VBAK.
Next options:
• "Regenerate as Excel"
• "Extend to L4 with Where-used"
• "Add an English version"
</Output_Format>
<MCP_Tools_Used>
SearchObject, GetObjectInfoGetProgFullCode, GetIncludesList, GetIncludeReadClass, ReadFunctionModule, ReadInterface, ReadViewRead BehaviorDefinition, Read BehaviorImplementation, Read ServiceDefinition, Read ServiceBindingGetLocalDefinitions, GetLocalMacros, GetLocalTestClass, GetLocalTypesGetScreensList, GetGuiStatusList, GetTextElementGetMetadataExtensionGetAbapAST, GetAbapSemanticAnalysisGetWhereUsed, GetEnhancements, GetEnhancementSpot
</MCP_Tools_Used><Related_Skills>
/sc4sap:analyze-code — code quality review (what's wrong)/sc4sap:create-program — spec → new program (forward direction)/sc4sap:deep-interview — requirement clarification for new builds
</Related_Skills><Data_Extraction_Safety>
Spec generation only reads source code + DDIC metadata + where-used — never GetTableContents / GetSqlQuery. No row data is extracted. The blocklist hook is respected if the user asks for sample data (refuse and document the request in the Risk sheet instead).
</Data_Extraction_Safety>
<Inputs_And_Screens_Rendering>
xlsx output — always-on pipeline (clone + program-specific imagery): every xlsx spec runs scripts/spec/build-spec.mjs <tr.json> <image-spec.json> <out.xlsx>. The helper clones asset/template_base.xlsx (geometry / styles / fonts / column widths / row heights / image anchors — all preserved), renders three program-specific PNGs from image-spec.json, then swaps them into the cloned xlsx with dynamic <xdr:ext> extents (no stretching). Three image slots are populated on every spec:
xl/media/image2.png at C4) — driven by image-spec.json.selectionxl/media/image1.png at C19) — driven by image-spec.json.alvxl/media/image3.png at B19, horizontal layout) — driven by image-spec.json.processFlow (each program has a different flow, so drawing4.xml is injected on demand from a blank template container)Graceful degrade: if no headless browser is on PATH, renderScreenImages returns null per slot and build-spec.mjs keeps the template mockups for that slot — never crashes.
No trigger keywords required. Image rendering is part of the default Excel pipeline because each program has unique selection screens, ALV layouts, and flow charts. Drift risk applies only to geometry regression (the old throwaway-driver problem) and image swap only touches drawing extents + PNG bytes, not geometry.
Markdown output — unchanged: continue emitting ASCII wireframes inside fenced code blocks (Step 3.5 in workflow-steps.md). ASCII wireframes never go in xlsx cells.
</Inputs_And_Screens_Rendering>
Task: {{ARGUMENTS}}
npx claudepluginhub babamba2/superclaude-for-sap --plugin sc4sapGenerates formal software specification documents (SPEC) from existing Delphi source code by reverse-engineering requirements, business rules, data models, and integrations directly from `.pas`, `.dfm`, `.dpr` files.
Explains ABAP objects with full dependency context via SAPContext and optional ATC code quality analysis. Supports classes, CDS views, behavior definitions (BDEF), reports, and more.
Creates new ABAP programs (Report, CRUD, ALV, Batch) with Main+Include structure supporting OOP or Procedural paradigms using a multi-phase coding and QA pipeline.