ABAP development skill for SAP ECC 6.0 EHP8 (NetWeaver 7.50, ABAP 7.50). Also SAP CRM in version EHP4 FOR SAP CRM 7.0 Use when writing ABAP code, working with internal tables, structures, Open SQL, object-oriented programming, string processing, dynamic programming, RTTI/RTTC, field symbols, data references, exception…
Amrize BP knowledge base for SAP ECC development decisions. Use when planning, designing, implementing, or reviewing ABAP developments, change requests (CHG), WRICEF objects, Mulesoft/Salesforce integrations, enhancement spots, FM facades, OO architecture, or deploy workflows. Provides naming conventions, coding…
Executes a specific task from tasks.md for a given change request. Use when implementing ABAP code, creating or updating SAP objects based on an approved design.
Scaffolds a new Change Request folder using Kiro-native spec structure. Use when starting a new CHG — provide the change number and a short description name.
Reads requirements and WRICEF metadata, generates design.md and tasks.md for a CHG. Use when starting technical planning after requirements are defined.
Investigates the SAP system to validate a specification's feasibility against existing objects, workflows, and data structures. Produces an analysis document with findings. Use before planning when you need to understand what exists in the system first.
Pulls the latest hooks, steering, skills, specs template, and workspace definitions from the remote GitHub template repo into the current workspace. Use when you want to update your local environment with the latest shared standards.
Extracts template-worthy improvements from the current workspace and syncs them to the shared template repo. Use after refining skills, steering, hooks, or specs structure during real project work.
Independently checks an executed task against requirements.md before the transport is released. Use after code has been pushed to SAP to validate correctness, technology compliance, and spec alignment.
★not rated 0 yesterdayA37 tokens
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: