Skip to main content
command CX Codex

design-nurture — Claude Code command: what it does, how to install

design-nurture builds multi-stage nurture journey blueprints with audience segmentation, triggers, and a content plan. Useful for planning lifecycle marketing and RevOps campaigns.

Apache-2.0 ★ 450 updated 2026-04-03

Install into Claude Code · Manually: put the files in place All methods and platforms ↓
.claude/commands/design-nurture.md
Open on GitHub

What design-nurture does

The command designs end-to-end nurture flows. It structures campaign objectives such as pipeline generation, expansion, adoption, education, or reactivation, then assigns triggers and suppression rules across channels like email, in-app messaging, ads, or SDR outreach.

Output deliverables include a journey table, Mermaid diagrams or automation pseudo-code, an asset delivery checklist, and a plan schema saved to .claude/plans/plan-<timestamp>.json. The workflow is orchestrated by nurture-architect along with the lifecycle-cadence and personalization-logic skills.

Validation failures trigger an escalation flow toward marketing ops and RevOps if the default limit of 2 retries is exceeded.

What it helps with

  • Build multi-stage nurture architectures for targeted audience segments
  • Map touchpoints, triggers, and content offers across email and SDR channels
  • Generate Mermaid journey diagrams and branching rules for marketing operations
  • Save structured JSON journey plans for execution audits in Claude Code

Example prompts for the agent

  • /lead-nurture-orchestration:design-nurture --goal pipeline --segments "mid-market,enterprise" --length 6
  • /lead-nurture-orchestration:design-nurture --goal expansion --segments "tier-1-accounts" --length 5 --channels "email,in-app,SDR assist"

How to install design-nurture

Manually: put the files in place

.claude/commands/design-nurture.md

Call it with /design-nurture. For all projects use ~/.claude/commands/

Questions about design-nurture

How to install design-nurture in Claude Code?

Place the command markdown file at .claude/commands/design-nurture.md in your project directory.

What does design-nurture do?

It creates multi-stage lead nurture blueprints, covering lifecycle stages, segmentation triggers, fallback branches, and output tables with Mermaid diagrams.

What parameters are required by design-nurture?

You must provide --goal, --segments, and --length, along with optional flags for --channels and brand or compliance --constraints.

Source text

design-nurture.md · Apache-2.0
---
name: design-nurture
description: Produces a multi-stage nurture journey blueprint with segmentation, triggers, and content plan.
usage: /lead-nurture-orchestration:design-nurture --goal pipeline --segments "mid-market,enterprise" --length 6
---

# Command: design-nurture

## Inputs
- **goal** – pipeline, expansion, adoption, education, reactivation.
- **segments** – comma-separated audiences.
- **length** – desired number of steps/stages.
- **channels** – optional list (email, in-app, ads, SDR assist).
- **constraints** – optional compliance/brand limitations.

### GTM Agents Pattern & Plan Checklist
> Derived from GTM Agents orchestrator blueprint @puerto/plugins/orchestrator/README.md#112-325.

- **Pattern selection**: Most nurture builds follow a **pipeline** (brief → architecture → content → branching → measurement). Switch to **diamond** when content mapping and personalization work can run in parallel. Document the pattern in the plan header.
- **Plan schema**: Save `.claude/plans/plan-<timestamp>.json` with objective, stages, task IDs, parallel groups, context passing (e.g., audience segments), error handling, and success criteria (activation, SQL lift, etc.).
- **Tool hooks**: Reference `docs/gtm-essentials.md` (Serena for MAP/CRM automation patches, Context7 for platform docs, Sequential Thinking for retros, Playwright for landing/in-app QA).
- **Guardrails**: Set retry limits (default 2) and escalation flow (Nurture Architect → Marketing Ops Lead → RevOps) if automation validation fails.
- **Review**: Use `docs/usage-guide.md#orchestration-best-practices-puerto-parity` checklist before execution to confirm agents, dependencies, deliverables.

## Workflow
1. **Brief Alignment** – confirm ICP, lifecycle stage, KPIs, and signal availability.
2. **Stage Architecture** – define entry criteria, triggers, and suppression per segment.
3. **Content Mapping** – outline assets, offers, personalization tokens per touch.
4. **Branching & Fail-safes** – specify conditional logic, fallback steps, exit rules.
5. **Measurement Plan** – KPIs per stage, alerting, retro cadence, experiment backlog.

## Outputs
- Journey table (step, trigger, channel, asset, CTA, owner).
- Mermaid-style diagram or pseudo-code for automation teams.
- Asset + data requirements list with due dates and owners.
- Plan JSON entry stored/updated in `.claude/plans` for audit trail.

## Agent/Skill Invocations
- `nurture-architect` – leads design.
- `lifecycle-cadence` skill – validates pacing + suppression.
- `personalization-logic` skill – ensures tailored content blocks.

## GTM Agents Safeguards
- **Fallback agents**: note substitutions (e.g., Marketing Ops Partner covering Personalization) if a specialist is unavailable.
- **Escalation triggers**: if guardrails (drop-off %, unsubscribe, latency) breach twice within 48h, escalate per lifecycle rip-cord (Marketing Director + Sales Director).
- **Plan maintenance**: When segments, owners, or branching logic change, update the saved plan and reference change log in status packets.

---

© gtmagents · Apache-2.0 · gtmagents/gtm-agents

Similar slash commands

All slash commands for Marketing and content →

From the same set224

The whole set →
creative-iteration-playbook creative-iteration-playbook turns social creative work into briefs, test matrices, a production pipeline and stop thresholds for paid campaigns. CX Codex +1 ★ 450repo stars plan-loyalty plan-loyalty generates a loyalty program blueprint with tier structures, customer incentives, and lifecycle triggers within a set budget. CX Codex +1 ★ 450repo stars manage-production The manage-production command turns a campaign and its assets into a production tracker with owners, review steps, and QA. Use it to plan work across several deliverables. CX Codex +1 ★ 450repo stars design-referral design-referral is a Claude Code command that designs referral programs with incentives, rules, and governance, producing a charter, stakeholder deck, and risk log. CX Codex +1 ★ 450repo stars run-launch The run-launch command builds a launch execution plan with a timeline, communications, monitoring, and go/no-go gates. Use it to coordinate channel work and launch-day operations. CX Codex +1 ★ 450repo stars build-model The build-model command builds a data modeling plan: transforms, tests, deployment schedule and dependencies for analytics use cases. CX Codex +1 ★ 450repo stars monitor-sla monitor-sla tracks MQL to SQL SLA compliance, highlights routing bottlenecks, and suggests corrective steps across marketing and sales pipelines. CX Codex +1 ★ 450repo stars ship-dashboards ship-dashboards builds a dashboard launch plan covering visualization, publishing, user enablement, and monitoring. Use it to coordinate the rollout and define what to track afterward. CX Codex +1 ★ 450repo stars

Project sponsors

Companies that keep this analytics open