sap-session

Orchestrate multi-turn SAP diagnosis workflows across modules without live system access.

16|6|Updated Apr 11, 2026
One-click install
npx skills add https://github.com/BoxLogoDev/sapstack --skill sap-session
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sap-session
Source: https://github.com/BoxLogoDev/sapstack/tree/main/plugins/sap-session/skills/sap-session
Command: npx skills add https://github.com/BoxLogoDev/sapstack --skill sap-session

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Evidence Loop-based SAP diagnostics often require live system access and coordination across multiple expert roles. sap-session provides a safe, turn-based orchestrator that lets humans collect evidence while the AI generates hypotheses, verifies results, and suggests fixes, enabling diagnosis without direct live access.

Core Features & Use Cases

  • Orchestrates 18 SAP modules (FI, CO, TR, MM, SD, PP, HCM, PM, QM, WM, EWM, ABAP, BASIS, S4MIG, BC, Cloud PE, and more) and 15 consultant agents.
  • Implements a Turn-aware workflow (Intake → Hypothesis → Collect → Verify) with persistent session state and evidence bundles.
  • Supports multi-surface interaction (CLI, VS Code extension, web portal) for operator and end-user workflows.
  • Facilitates compliant, auditable governance including session-state, evidence tracking, and rollback planning.

Quick Start

Start a new sap-session with the CLI by providing your initial symptom and optional first evidence bundle, then proceed with /sap-session-next-turn to begin hypothesis generation.

Frequently Asked Questions about sap-session

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

FAQPage Schema
How do I run SAP diagnostics without live system access?

You orchestrate SAP diagnostics without live system access using a turn-based Evidence Loop where humans collect evidence and AI generates hypotheses, verifies results, and suggests fixes across modules like FI, CO, MM, and SD.

What is the Evidence Loop workflow for SAP troubleshooting?

The Evidence Loop workflow for SAP troubleshooting follows a four-turn sequence: Intake, Hypothesis, Collect, and Verify. It maintains persistent session state and evidence bundles to ensure auditable, rollback-ready fixes across 18 SAP modules and 15 consultant agents.

How do I start a multi-turn SAP diagnosis session?

To start a multi-turn SAP diagnosis session, provide your initial symptom and an optional first evidence bundle via the CLI, then issue the next-turn command to begin AI hypothesis generation. The session tracks state across CLI, VS Code, or web portal surfaces.

Can I use AI orchestration for SAP module troubleshooting across FI and CO?

Yes, AI orchestration supports SAP module troubleshooting across FI, CO, TR, MM, SD, PP, HCM, PM, QM, WM, EWM, ABAP, BASIS, S4MIG, BC, Cloud PE, and more. It coordinates 15 consultant agents to streamline intake, hypothesis, collection, and verification turns.

Does SAP session orchestration support rollback planning and audit tracking?

SAP session orchestration supports rollback planning and audit tracking by enforcing schemas and persistent session-state tracking. It maintains evidence bundles throughout the Intake, Hypothesis, Collect, and Verify workflow to enable compliant, auditable governance.

What are the limitations of turn-based SAP diagnosis without direct system access?

Turn-based SAP diagnosis without direct system access relies on human-collected evidence rather than live queries, meaning it cannot autonomously pull real-time data. It requires operators to manually supply evidence bundles for the AI to generate hypotheses and verify results.