一键导入
zuora-uat-generate-feature
Internal worker — plan + generate-api + generate-ui + optional verify for one feature
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Internal worker — plan + generate-api + generate-ui + optional verify for one feature
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 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-generate-feature |
| description | Internal worker — plan + generate-api + generate-ui + optional verify for one feature |
Inputs: feature, optional tr_filter (TR numbers), force_overwrite, verify, environment, max_fix_retries.
${CLAUDE_PLUGIN_ROOT}/skills/zuora-uat/plan/SKILL.mdgenerate-api/SKILL.md (gap-fill)generate-ui/SKILL.md when hybrid (gap-fill)python3 "${CLAUDE_PLUGIN_ROOT}/references/uat-test/execution/scripts/uat_verification.py" clear \
--scenario-dir "$UAT_ROOT/execution/tests/test_scenarios/<folder>" --tr <n>
verify=true — verify/SKILL.md with environmentverify=false: set verified: false for affected TRs (same clear command as step 5, per TR in scope)python3 "${CLAUDE_PLUGIN_ROOT}/references/uat-test/execution/scripts/uat_verification.py" finalize-generate \
--git-root "$GIT_ROOT" \
--feature "<feature>" \
--verify "<verify>"
# append --tr N when tr_filter is set
Fail fast if ui_steps_tr{n}.md is missing from execution or present under testplan:
# A. Execution doc must exist
PYTHONPATH="$UAT_ROOT/execution/tests" python3 -c \
"from test_utils.repo_paths import resolve_ui_steps_doc_path; resolve_ui_steps_doc_path('<feature>', '<TRn>')"
# B. No stray UI docs in testplan for this feature
test -z "$(find "$UAT_ROOT/design/testplan" -path '*<feature>*' -name 'ui_steps_tr*.md' -print)"
On failure: move misplaced file from testplan to the resolved execution path (or delete and rewrite), then retry the check once. If still failing, return worker JSON with a failures entry for that TR.
tr_filter null → all TRs from plan folderPath: execution/tests/test_scenarios/test_<feature>/.uat-verification.json
Use uat_verification.py helpers from ${CLAUDE_PLUGIN_ROOT}/references/uat-test/execution/scripts/.
{
"feature": "<stem>",
"tr_filter": ["TR1"],
"status": "completed",
"artifacts": { "created": [], "skipped": [] },
"verification": { "TR1": { "verified": true, "artifact_revision": "abc123" } },
"execution": {},
"failures": []
}
Return only this summary to the parent orchestrator.