sap-abap-automated-documentationlisted

# SAP ABAP Automated Documentation Adapt the four-stage upstream prompt workflow to the router's registered capabilities. ## 1. Discover and plan - Identify the root object, package, transactions, includes, classes, function groups, interfaces, tables, customizing, enhancements, and dependencies. - Prefer ADT/code-search providers for source retrieval. Retrieve all relevant custom includes; do not recursively expand SAP-standard objects unless needed to explain an interface. - Present an evidence-backed plan when scope or live-system interaction is material. ## 2. Write documentation Cover overview, business context, user flow, inputs and outputs, examples, technical architecture, object details, data flow, structures, error handling, enhancements, full object inventory, and glossary. Use tables for object and parameter inventories. Use Mermaid only when it clarifies relationships, and accompany every diagram or screenshot with explanatory text. Prefer concise significant snippets over full source listings. For large deliverables, split chapters as `{OBJECT_NAME}_documentation_chapter_{N}.md`, then combine them in numeric order. Do not impose the upstream 4,000-character limit unless the active environment requires it. ## 3. Optional SAP GUI screenshots - Use the configured SAP GUI provider only with an existing authorized session. - Inspect and verify the screen before every interaction; keep navigation read-only unless the user explicitly authorizes a mutation. - C