Sc4sap:analyze Cbo Obj

SC4SAP Analyze CBO Objects

Walks a CBO (Customer Business Object) package, inventories every project-built ABAP element (table, structure, data element, class, interface, function module, program, view, table type), detects which elements are frequently reused inside the package, infers each element's business purpose from its name/fields/descriptions, and persists the result to .sc4sap/cbo/<MODULE>/<PACKAGE>/ for downstream skills (program, program-to-spec, create-object, autopilot) to consult before creating anything new.

Invoke /sc4sap:trust-session with parent_skill=sc4sap:analyze-cbo-obj to pre-grant all MCP tool + file-op permissions for this session (eliminates per-tool "Allow this tool?" prompts during the 8-step walk).

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

• Step 1 / 1.5 / 2 (main thread) — Socratic intake: package name → flagship programs (optional <KEY_PROGRAMS>) → module. Frontmatter pins the main thread to Sonnet 4.6.
• Step 3–7 (delegated · Sonnet 4.6) — One Agent(...) dispatch to sap-stocker. The stocker runs its own Investigation_Protocol: walk → GetWhereUsed graph → pin/frequency tiering → business-purpose inference → cross-module gap analysis (per ../../common/active-modules.md) → sensitive-name flagging → persist index.md + inventory.json → return a Logic-heavy: <bool> flag. Authoritative spec: ../../agents/sap-stocker.md § Investigation_Protocol + § Output_Format.
• Step 8 (branching):
  • Branch A (Logic-heavy: false, DDIC-dominant) — canned summary printed by main thread. No agent dispatch.
  • Branch B (Logic-heavy: true, FM/CLAS/INTF/large-PROG in inventory) — main thread renders a reader-facing briefing from inventory.json: pinned highlights · business-logic assets · cross-module gaps · sensitive objects · next-step hint. No extra agent dispatch.

Main thread NEVER calls GetPackageContents / GetWhereUsed itself for the inventory pass — that context stays inside the stocker so the orchestrator window remains small even for large packages (200+ objects).

Task: {{ARGUMENTS}}