configure-rewards — Claude Code command: what it does, how to install
configure-rewards orchestrates reward catalog setup, fulfillment workflows, and QA verification prior to a loyalty program launch.
Apache-2.0 ★ 450 updated 2026-04-03
.claude/commands/configure-rewards.mdWhat configure-rewards does
The command runs a five-stage preparation pipeline: reward intake, fulfillment design, compliance and risk verification, QA testing, and launch packet delivery. It engages reward-operations and loyalty-strategist agents alongside reward-ops and loyalty-modeling skills to align operations with business targets.
Execution state is tracked inside .claude/plans/plan-<timestamp>.json with dependency maps covering legal, finance, and vendor stakeholders. A default retry limit of 2 triggers an escalation ladder toward Reward Ops and executive sponsors whenever catalog imports or tests fail repeatedly.
What it helps with
- build a fulfillment runbook and SLA guidelines for operations teams
- validate tax compliance and fraud safeguards before release
- generate an audit trail inside
.claude/plansJSON plan files - execute redemption QA across tiers, devices, and failure paths
Example prompts for the agent
- /loyalty-lifecycle-orchestration:configure-rewards --program "Tiered Loyalty" --catalog drive://loyalty --launch-date 2026-01-15
- /loyalty-lifecycle-orchestration:configure-rewards --program "VIP Perks" --catalog docs/rewards.md --launch-date 2026-06-01 --regions US,EU
How to install configure-rewards
Manually: put the files in place
.claude/commands/configure-rewards.mdCall it with /configure-rewards. For all projects use ~/.claude/commands/
Manually: put the files in place
~/.codex/prompts/configure-rewards.mdCall it with /prompts:configure-rewards. Codex marks this format deprecated in favour of skills
Manually: put the files in place
.github/prompts/configure-rewards.prompt.mdManually: put the files in place
.gemini/commands/configure-rewards.tomlGemini stores commands as TOML: the prompt text goes into the prompt field
Questions about configure-rewards
How to install configure-rewards in Claude Code?
Place the command specification file into .claude/commands/configure-rewards.md.
What does configure-rewards do?
It orchestrates reward definitions, automates notification and fulfillment workflows, checks tax rules, and outputs launch checklists.
How does the command handle test failures?
It enforces a retry limit of 2 and escalates unresolvable issues through Reward Ops, Legal/Finance, and the project sponsor.
Source text
configure-rewards.md · Apache-2.0
--- name: configure-rewards description: Orchestrates reward catalog setup, fulfillment workflows, and QA before launch. usage: /loyalty-lifecycle-orchestration:configure-rewards --program "Tiered Loyalty" --catalog drive://loyalty --launch-date 2026-01-15 --- # Command: configure-rewards ## Inputs - **program** – reference name/ID for the loyalty initiative. - **catalog** – storage location or doc with reward definitions. - **launch-date** – target go-live date. - **regions** – optional localization list for compliance and fulfillment. - **approvers** – optional stakeholders (legal, finance, partner, ops). ### GTM Agents Pattern & Plan Checklist > Mirrors GTM Agents orchestrator blueprint @puerto/plugins/orchestrator/README.md#112-325. - **Pattern selection**: Reward configuration usually runs **pipeline** (catalog intake → fulfillment design → compliance QA → launch packet). If QA + compliance run in parallel, document a **diamond** block with merge gate in the plan header. - **Plan schema**: Save `.claude/plans/plan-<timestamp>.json` capturing catalog source, fulfillment automations, dependency graph (legal, finance, ops, vendors), error handling, and success metrics (SLA, redemption accuracy, fraud rate). - **Tool hooks**: Reference `docs/gtm-essentials.md` stack—Serena for catalog diffs, Context7 for compliance/billing SOPs, Sequential Thinking for QA retros, Playwright for redemption form testing. - **Guardrails**: Default retry limit = 2 for failed catalog loads or QA runs; escalation ladder = Reward Ops → Finance/Legal → Exec sponsor. - **Review**: Run `docs/usage-guide.md#orchestration-best-practices-puerto-parity` before launch to confirm dependencies + approvals. ## Workflow 1. **Catalog Intake** – load reward definitions (cost, eligibility, inventory) plus vendor details. 2. **Fulfillment Design** – define earning/redemption automations, notification flows, and SLA tracking. 3. **Compliance & Risk** – validate tax regulations, export controls, and fraud safeguards. 4. **QA Checklist** – run test transactions across tiers, currencies, devices, and failure scenarios. 5. **Launch Packet** – produce runbook, escalation plan, and monitoring dashboard references. ## Outputs - Reward configuration checklist with owner + status. - QA evidence (screenshots, logs, test cases) stored with catalog. - Fulfillment runbook (SLA, webhook IDs, contact points) for ops + support teams. - Plan JSON entry stored/updated in `.claude/plans` for audit trail. ## Agent/Skill Invocations - `reward-operations` – leads fulfillment + QA steps. - `loyalty-strategist` – approves benefit alignment with goals. - `reward-ops` skill – enforces operational standards. - `loyalty-modeling` skill – confirms economics after final catalog changes. ## GTM Agents Safeguards - **Fallback agents**: document substitutes (e.g., Reward Ops covering Strategist) when approvers unavailable. - **Escalation triggers**: escalate if QA fails twice or compliance issues surface; follow GTM Agents rip-cord and log remediation inside plan JSON. - **Plan maintenance**: update plan JSON/change log whenever catalog, vendors, or launch dates shift for audit parity. ---
© gtmagents · Apache-2.0 · gtmagents/gtm-agents