name: cap-change-workflow
description: 'Use for end-to-end CAP change workflows: modify CDS/handlers, regenerate artifacts, and run a short verification checklist for this repository.'
argument-hint: 'Describe the CAP change to implement and verify'
user-invocable: true
disable-model-invocation: false
CAP Change Workflow
Use this skill when implementing non-trivial CAP changes (CDS, services, handlers, annotations) and you want a consistent implementation + verification flow.
When to use
Adding/changing entities, associations, projections, or service exposure
Updating
cap/srv/*.jshandlers or event hooksRegenerating build artifacts and validating basic runtime behavior
Procedure
Clarify requested behavior and impacted files.
If CDS is involved:
Resolve definitions with cds-mcp first.
Check CAP docs with cds-mcp before proposing CAP API/CLI syntax.
Implement minimal changes in appropriate layer:
cap/dbfor domain modelcap/srv/*-service.cdsfor contractscap/srv/*-fiori.cdsfor UI annotationscap/srv/*.jsfor runtime logic
Rebuild artifacts in
cap/(npm run build) when CDS changed.Run a compact verification checklist and report outcomes.
Document risks, assumptions, and follow-ups.
Repository gotchas
After HANA deployment, generated folders can be cleared; run
npm run buildagain.SQLite local loading may hit
SQLITE_BUSYwith parallel loading.
Checklist template
Use this checklist after implementation: assets/change-checklist.md.