Menu
Internal UI test doc generation for hybrid TRs
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
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-generate-ui |
| description | Internal UI test doc generation for hybrid TRs |
Creates execution/tests/test_scenarios/test_<feature>/ui_steps_tr{n}.md when the plan marks UI Test Doc Required: Yes.
Never write ui_steps_tr{n}.md under design/testplan/ — that folder is design-only (plan overview + per-TR test design).
Use execution/tests/test_utils/repo_paths.py from the customer repo (copy any missing files from ${CLAUDE_PLUGIN_ROOT}/references/uat-test/execution/tests/test_utils/):
resolve_feature_scenario_dir(feature) — target scenario directoryresolve_ui_steps_doc_path(feature, tr_index) — final write path (raises if missing; use parent dir for writes)Resolve the scenario directory before writing; output must land beside the API script for the same TR.
Skip when force_overwrite=false and ui_steps_tr{n}.md already exists at the resolved execution path (not under testplan).
Follow ${CLAUDE_PLUGIN_ROOT}/references/uat-test/execution/docs/UI_TEST_DOC_FORMAT.md.
Include: prerequisites, debug log variable references, numbered UI steps, expected outcomes.
mcp__zuora-mcp__ask_zuora for UI navigation paths when not in the test design. No Playwright during generation.