AI Agent Workflow Collection

Use when writing, reviewing, or troubleshooting ABAP Cloud code, RAP business objects, CDS views, released APIs, or any ABAP development in S/4HANA Public Cloud or BTP ABAP Environment.

Use when working with SAP Ariba — Ariba Network, Guided Buying, Sourcing, Contracts, Supplier Lifecycle Management, Supplier Risk Management, Procurement, Invoice Management, integration with S/4HANA via CIG, catalog management, or Ariba APIs.

Use when working with SAP Concur — Concur Expense, Concur Travel, Concur Invoice, Concur Request, expense policy configuration, receipt management, travel booking, approval workflows, integration with S/4HANA FI, audit rules, or compliance monitoring.

Use when the user wants to produce all deliverables for an SAP Activate phase in one orchestrated run. This is the factory — it chains skills, dispatches agents in parallel, collects artifacts, and produces a phase-complete deliverable package with quality scoring.

Use when working with SAP Fieldglass — contingent workforce management, services procurement, Statement of Work (SOW), worker management lifecycle, rate card management, approval workflows, VMS reporting, or Fieldglass integration with S/4HANA.

Use when classifying business requirements against SAP standard capability during Explore phase. Triggers on requests to assess coverage, identify gaps, classify requirements, determine custom development need, or build a fit-gap matrix.

Use when assessing SAP go-live readiness, producing a Go/No-Go decision, or evaluating whether a system is ready for production. Triggers on any request involving go-live approval, readiness assessment, go/no-go checklist, production launch sign-off, or cutover gate review.

Use when managing SAP post-go-live hypercare, setting up a hypercare war room, triaging live production issues, tracking stabilization, planning hypercare exit, or transitioning support to BAU. Triggers on any request involving post-go-live support, day-one issues, hypercare period, stabilization criteria, or support handover.

Use when designing, building, troubleshooting, or reviewing SAP Integration Suite artifacts — Cloud Integration (CPI) iFlows, API Management proxies, Integration Advisor B2B templates, Event Mesh, or any middleware pattern connecting SAP and non-SAP systems.

Use when designing SAP business processes during Explore or Realize phases. Triggers on requests to map current processes, design future-state processes, define process variants, assign process owners, set KPIs, or align to SAP Best Practices.

Use when reverse-engineering an existing ABAP program into a functional or technical specification. Reads code and produces structured documentation — not a code dump, a proper spec document that a consultant can hand to a client.

Use when advising on S/4HANA migration approach, assessing greenfield vs brownfield vs selective data transition options, analyzing custom code impact, reviewing simplification items, or building a migration business case or timeline.

Use when diagnosing plugin health, MCP server connectivity, SAP system connection issues, or configuration problems. Runs systematic health checks and produces a diagnostic report.

Use when generated or modified ABAP code has syntax errors, ATC findings, test failures, or activation issues. Runs an iterative fix-check-fix loop until the code is clean, tested, and activated. Equivalent to a persistent development TDD cycle.

Use when the user wants a pre-built, industry-aware solution package for a common SAP end-to-end process. Accelerators provide 60% pre-filled deliverables, pre-mapped process flows, known gap patterns, and proven configuration sequences — cutting weeks of discovery into hours.

Use when a task requires parallel work by multiple specialized agents — e.g., simultaneous code review + security audit + performance check, or multi-object development where different agents handle different components. Orchestrates agent dispatch, manages dependencies, and merges results.

Use when releasing transport requests through the SAP transport landscape. Enforces pre-release checks, dependency validation, and proper CTS workflow — DEV → QAS → PRD with quality gates at each stage.

Injected at session start. Use when any SAP-related question, task, or project is detected. Governs skill routing, workflow chains, knowledge retrieval, and agent delegation for the entire SAP Superpowers system.

Use when building a business case, calculating ROI or TCO, quantifying SAP project benefits, validating savings claims, or producing value realization frameworks for any SAP investment decision.

Use when creating, reworking, reviewing, or improving any SAP Superpowers skill file. Triggers on requests to write a skill, update a skill, add a section to a skill, or pressure-test a skill.