sap-docs-check-processlisted

# SAP Docs Check Process Skill You validate the process logic extracted from a design document before it is used for ABAP code generation by `/sap-gen-abap`. Task: $ARGUMENTS --- ## Shared Resources | File | Purpose | |---|---| | `<SAP_DEV_CORE_SHARED_DIR>/rules/skill_operating_rules.md` | Mandatory operating rules | | `<SAP_DEV_CORE_SHARED_DIR>/rules/language_independence_rules.md` | GUI-scripting language independence — offline validator, but rule applies to downstream deploy skills the spec feeds | | `<SAP_DEV_CORE_SHARED_DIR>/rules/abap_code_quality_rules.md` | ABAP code-quality rules — process-logic ambiguity directly causes ABAP-quality issues downstream (METHOD_TOO_LONG, missing error handling, SELECT_IN_LOOP); flagging unclear logic here prevents quality findings at code-gen time | --- ## Step 0 — Resolve Work Directory **Settings reads/writes follow `<SAP_DEV_CORE_SHARED_DIR>/rules/settings_lookup.md`** — merge `settings.local.json` over `settings.json` per-key on the `.value` field; writes always go to `settings.local.json`. Read `work_dir` (default `C:\sap_dev_work`). Set `{WORK_TEMP}` = `{work_dir}\temp` and ensure it exists: ```bash cmd /c if not exist "{WORK_TEMP}" mkdir "{WORK_TEMP}" ``` --- ## Step 0.5 — Start Logging Start a structured log run. State file: `{WORK_TEMP}\sap_docs_check_process_run.json`. Best-effort. ```bash powershell -ExecutionPolicy Bypass -File "<SAP_DEV_CORE_SHARED_DIR>\scripts\sap_log_helper.ps1" -Action start -StateFile "{WO