sap-superpowers

consulting skills category for SAP Superpowers. Contains 9 sub-skills.

delivery skills category for SAP Superpowers. Contains 6 sub-skills.

development skills category for SAP Superpowers. Contains 8 sub-skills.

meta skills category for SAP Superpowers. Contains 7 sub-skills.

modules skills category for SAP Superpowers. Contains 20 sub-skills.

strategic skills category for SAP Superpowers. Contains 5 sub-skills.

Use when eliciting requirements, mapping business processes, analyzing pain points, generating solution options, or conducting structured ideation for SAP implementations. Triggers on brainstorm, ideation, requirements gathering, process mapping, or pain point analysis.

Use when planning or executing organizational change for an SAP implementation. Triggers on requests for stakeholder impact analysis, change readiness assessment, communication planning, training needs analysis, resistance management, or adoption measurement.

Use when gathering requirements for an SAP project, feature, or change request. Conducts a structured Socratic interview to extract complete, unambiguous requirements — preventing scope creep, missed edge cases, and assumption-based development.

Use when estimating effort, timelines, or complexity for SAP work items, sprints, phases, or full projects. Triggers on requests for hours, days, duration, cost, resource count, or project sizing.

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 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 starting a new SAP project, setting up governance, defining scope, identifying stakeholders, creating a project charter, or establishing a RACI matrix for any SAP Activate engagement.

Use when designing SAP solution landscapes, defining integration architecture, making BTP vs on-premise decisions, creating extensibility strategies, or producing solution architecture documents for any SAP implementation.

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 planning, sequencing, or executing SAP cutover activities including go-live weekend tasks, system switchover, data migration execution, interface activation, rollback planning, or cutover rehearsal. Triggers on any request involving cutover, production go-live execution, T-minus schedule, or cutover runbook.

Use when planning, designing, or executing SAP data migration. Triggers on requests involving data migration strategy, data mapping, LTMC, BODS, legacy data conversion, reconciliation, trial migration, or cutover data load.

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, planning, or executing a testing strategy for an SAP implementation, upgrade, or change project. Triggers on any request involving test planning, UAT, test cases, test automation, defect management, or sign-off readiness.

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.

Use when the user wants end-to-end autonomous ABAP development — from idea to tested, activated, transport-ready code. Chains through requirements → design → generate → test → activate → verify in a single pipeline.

Use when generating ABAP, CDS, RAP, Fiori Elements, or BTP CAP code for SAP systems. Enforces cloud-ready, clean-core-compliant, testable code generation — not quick-and-dirty prototypes.

Use when reviewing ABAP code, SAP development artifacts, CDS views, or any custom SAP code before transport release, pull request approval, or go-live sign-off.

Use when starting SAP development work, creating transports, moving objects across landscapes, structuring packages, or any task involving DEV→QAS→PRD change management.

Use when diagnosing or resolving SAP performance problems — slow transactions, long-running batch jobs, expensive SQL, HANA resource issues, or general ABAP runtime bottlenecks.

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 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 diagnosing SAP runtime errors, performance issues, integration failures, or any unexpected system behavior. Enforces structured root cause analysis — not guessing.

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 diagnosing plugin health, MCP server connectivity, SAP system connection issues, or configuration problems. Runs systematic health checks and produces a diagnostic report.

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.

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 before claiming ANY task is complete. Activates at the end of every skill execution, every deliverable generation, and every user request fulfillment. Blocks completion claims that lack enumerated evidence.

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.

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 Analytics Cloud (SAC), embedded analytics in S/4HANA, CDS-based analytical views, KPI modeling, Fiori analytical apps, BW/4HANA, SAP Datasphere, planning models, or BI story design.

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 designing, building, or troubleshooting solutions on SAP Business Technology Platform — subaccounts, Cloud Foundry, Kyma, CAP, HANA Cloud, XSUAA, destinations, or any BTP service.