Menu
Internal worker — verify gate + execute-api + execute-ui for one feature
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Generate Credit Memos / Debit Memos migration implementation artifacts based on the plan
Produce Credit Memos / Debit Memos migration strategy, code inventory, and phases
This skill should be used when the user mentions "Zuora API", "Zuora SDK", "Zuora Billing", "Zuora Revenue", "Zuora CPQ", "Zuora Payments", "subscription billing", "invoice settlement", "zuora-mcp", "rate plan", "product rate plan charge", "order API", or discusses integration with Zuora systems. Do not activate for generic billing or subscription discussions that are not Zuora-specific.
Compose an importable Zuora Workflow JSON from a design or requirement
Design a Zuora Workflow-based solution
Generate legacy Zuora CPQ Apex, Visualforce, Component Library, zQuoteUtil, controller extension, or plugin-interface artifacts directly into a Salesforce DX repo
| name | zuora-uat-run-feature |
| description | Internal worker — verify gate + execute-api + execute-ui for one feature |
Inputs: feature, optional tr_filter, verify (auto|true|false), environment, max_fix_retries.
Ensure a canonical verification manifest exists before any TR work:
python3 "${CLAUDE_PLUGIN_ROOT}/references/uat-test/execution/scripts/uat_verification.py" ensure-manifest \
--git-root "$GIT_ROOT" \
--feature "<feature>"
# When tr_filter is set, append --tr N for each TR in scope
Resolve scenario dir: $UAT_ROOT/execution/tests/test_scenarios/test_<feature>/ (via repo_paths.resolve_feature_scenario_dir).
verify | Behavior |
|---|---|
false | Execute directly; no fix/review |
true | Always run verify segment first |
auto | Run verify when mark missing, verified: false, or artifact_revision stale |
Check stale marks:
python3 "${CLAUDE_PLUGIN_ROOT}/references/uat-test/execution/scripts/uat_verification.py" should-verify \
--scenario-dir "<scenario_dir>" --tr <n> --git-root "$GIT_ROOT" --feature "<feature>"
Exit 0 → run verify; exit 1 → skip verify.
verify/SKILL.md. On failure: skip execute for this TR.execute-api/SKILL.mdpython3 "${CLAUDE_PLUGIN_ROOT}/references/uat-test/execution/scripts/hybrid_tr_prepare.py" \
--git-root "$GIT_ROOT" \
--feature "<feature>" \
--tr <n> \
--environment "<environment>"
execute_ui | Action |
|---|---|
true | MUST run execute-ui/SKILL.md using variables, ui_steps_path, and debug_log from script output. Do not return worker JSON until UI completes or retries are exhausted. |
false | Record skip reason in worker JSON (execution.TRn.ui=skipped, execution.TRn.reason=<skip_reason>). Call record-ui-result with --status skipped --reason "<skip_reason>". |
python3 "${CLAUDE_PLUGIN_ROOT}/references/uat-test/execution/scripts/uat_verification.py" record-ui-result \
--scenario-dir "<scenario_dir>" \
--tr <n> \
--status passed|failed|skipped \
--evidence "<report_or_screenshot_path>" \
--summary "<one-line outcome>"
verified: true, artifact_revision){
"feature": "<stem>",
"tr_filter": ["TR1"],
"status": "completed",
"artifacts": {},
"verification": { "TR1": { "verified": true, "artifact_revision": "abc123" } },
"execution": {
"TR1": { "api": "passed", "ui": "passed", "evidence": "execution/reports/tr1_account_page.md" }
},
"failures": []
}
Return only this summary to the parent orchestrator.