abap-playbook

A Claude Code skill for ABAP development through the EPOD ADT MCP Server.

The skill runs larger development tasks through a phased playbook: discovery, plan, user approval, implementation, verification. Each phase is bound to the token-efficient MCP tools — member lists before source, element reads and writes instead of full pulls, one combined check call — and each phase ends with a gate.

Small tasks do not open the playbook. The skill applies process only where the task creates a new object, changes two or more objects, or must keep the current behaviour.

Installation

Copy the skill folder into your Claude Code skills directory:

git clone https://git.epod.dev/erhan/abap-playbook-skill.git
cp -r abap-playbook-skill ~/.claude/skills/abap-playbook

Requirements: Claude Code with the EPOD ADT MCP Server connected. The skill uses sap_object_members, sap_pull_source with element, sap_push_element, sap_push_source, sap_check_object, and sap_usage_references.

Contents

SKILL.md                        the skill: phases, gates, tool bindings
templates/playbook-template.md  the empty playbook a task fills in

The short version of the rules

1. Read structure before source. A full pull needs a written reason.
2. The filled playbook goes to the user before implementation. Always.
3. The object list in the plan is a contract.
4. One combined check call per object, not three.
5. A gate that fails two times stops the work. A third attempt costs more than a question.

License

Apache License 2.0. Copyright 2026 Erhan Keseli.