plan-loyalty — Claude Code command: what it does, how to install
plan-loyalty generates a loyalty program blueprint with tier structures, customer incentives, and lifecycle triggers within a set budget.
Apache-2.0 ★ 450 updated 2026-04-03
.claude/commands/plan-loyalty.mdWhat plan-loyalty does
The command guides loyalty architecture across five steps: reviewing churn and cohort revenue, drafting tier mechanics, embedding triggers into customer journeys, modeling program economics, and assigning governance owners. The resulting architecture is saved to .claude/plans/plan-<timestamp>.json alongside dependencies across finance, legal, and operations.
Execution relies on specialized agents: loyalty-strategist, loyalty-modeling, and member-insights-analyst. The workflow coordinates tools from docs/gtm-essentials.md, using Serena for catalog diffs, Context7 for compliance docs, Sequential Thinking for scenarios, and Playwright for redemption flow verification.
A repeated negative ROI projection or legal roadblock triggers an escalation ladder directly to finance and the executive sponsor.
What it helps with
- design loyalty tier requirements, earn rules, and member benefits
- map automated loyalty triggers into onboarding and renewal touchpoints
- model cost per point, breakage assumptions, and program break-even timing
- record operational dependencies and audit trails in structured plan files
Example prompts for the agent
- /loyalty-lifecycle-orchestration:plan-loyalty --goal retention --tiers 3 --budget 50000
- /loyalty-lifecycle-orchestration:plan-loyalty --goal expansion --tiers hybrid --budget 80000 --personas "enterprise, mid-market"
- /loyalty-lifecycle-orchestration:plan-loyalty --goal engagement --tiers missions --budget 20000 --constraints "GDPR compliance"
How to install plan-loyalty
Manually: put the files in place
.claude/commands/plan-loyalty.mdCall it with /plan-loyalty. For all projects use ~/.claude/commands/
Manually: put the files in place
~/.codex/prompts/plan-loyalty.mdCall it with /prompts:plan-loyalty. Codex marks this format deprecated in favour of skills
Manually: put the files in place
.github/prompts/plan-loyalty.prompt.mdManually: put the files in place
.gemini/commands/plan-loyalty.tomlGemini stores commands as TOML: the prompt text goes into the prompt field
Questions about plan-loyalty
How to install plan-loyalty in Claude Code?
Add the command file directly to .claude/commands/plan-loyalty.md inside your repository.
What does plan-loyalty do?
It outputs a loyalty blueprint table, a lifecycle trigger matrix, and an economic model summarizing reward costs and expected lift.
Where does the command store audit records?
It writes plan parameters and change logs directly to .claude/plans/plan-<timestamp>.json.
Source text
plan-loyalty.md · Apache-2.0
--- name: plan-loyalty description: Produces loyalty program blueprint with tiers, benefits, and lifecycle triggers. usage: /loyalty-lifecycle-orchestration:plan-loyalty --goal retention --tiers 3 --budget 50000 --- # Command: plan-loyalty ## Inputs - **goal** – retention | expansion | engagement | advocacy. - **tiers** – number of tiers or type (points-only, hybrid, missions). - **budget** – monthly/quarterly reward pool. - **personas** – optional comma-separated member segments. - **constraints** – optional compliance or platform notes. ### GTM Agents Pattern & Plan Checklist > Mirrors GTM Agents orchestrator blueprint @puerto/plugins/orchestrator/README.md#112-325. - **Pattern selection**: Loyalty design generally follows a **diamond** (research ↔ modeling in parallel, converge into governance) or **pipeline** if run sequentially; document choice in the plan header. - **Plan schema**: Save `.claude/plans/plan-<timestamp>.json` capturing tiers, benefit assumptions, financial guardrails, dependency graph (legal, finance, ops), error handling, and success criteria (retention, NRR, cost/point). - **Tool hooks**: Reference `docs/gtm-essentials.md` stack—Serena for catalog/tier diffs, Context7 for compliance docs, Sequential Thinking for scenario modeling, Playwright for testing redemption flows. - **Guardrails**: Default retry limit = 2 for data pulls or modeling errors; escalation ladder = Loyalty Strategist → Finance/Legal → Exec sponsor. - **Review**: Run `docs/usage-guide.md#orchestration-best-practices-puerto-parity` before publishing to ensure dependencies, approvals, and deliverables are logged. ## Workflow 1. **Signal Review** – pull churn metrics, cohort revenue, product usage, and VOC insights. 2. **Tier & Benefit Design** – outline requirements per tier (earn rules, benefits, surprise moments). 3. **Lifecycle Mapping** – embed loyalty triggers into onboarding, adoption, upsell, and renewal stages. 4. **Economic Modeling** – estimate cost per point, breakage, and projected ROI. 5. **Governance Packet** – assign owners, cadences, and KPIs for launch. ## Outputs - Program blueprint deck/table (tiers, requirements, benefits, KPIs). - Lifecycle trigger matrix (event → loyalty action → channel → owner). - Financial model summary (cost, expected lift, break-even timeline). - Plan JSON entry stored/updated in `.claude/plans` for audit trail. ## Agent/Skill Invocations - `loyalty-strategist` – leads architecture. - `loyalty-modeling` skill – calculates economics and guardrails. - `member-insights-analyst` – validates segment assumptions. ## GTM Agents Safeguards - **Fallback agents**: document substitutes (e.g., loyalty-ops covering strategist) when key approvers unavailable. - **Escalation triggers**: escalate if modeling shows negative ROI twice or compliance blockers arise; follow GTM Agents rip-cord path and log in plan JSON. - **Plan maintenance**: update plan JSON/change log whenever tiers, budgets, or guardrails shift so audit reviewers see history. ---
© gtmagents · Apache-2.0 · gtmagents/gtm-agents