Skip to main content
command CX Codex

implement-actions — Claude Code command: plans and setup

implement-actions is a Claude Code command that turns a prioritized customer-journey initiative into coordinated workstreams, ownership, and measurement.

Apache-2.0 ★ 450 updated 2026-04-03

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

What implement-actions does

The command breaks an initiative into workstreams and tasks, assigns owners, and records dependencies. It also lays out approvals, communications, enablement, and risk steps, then defines how teams will measure progress and review results after launch.

It stores a plan at .claude/plans/plan-<timestamp>.json, including task IDs, parallel groups, a dependency graph, error handling, and success metrics. Parallel work can include a merge gate. The workflow references Serena for instrumentation and configuration diffs, Context7 for SOPs, Sequential Thinking for retrospectives, and Playwright for experience QA when needed.

Blocked workstreams have a retry limit of 2, followed by escalation from the Journey Ops Owner to the CX Strategist and CX or Product leadership. Before execution, review docs/usage-guide.md#orchestration-best-practices-puerto-parity to check owners, dependencies, and deliverables.

What it helps with

  • split a journey initiative into owned workstreams
  • map dependencies across marketing, product, ops, and enablement
  • plan approvals and communications for a change
  • define KPIs and customer-feedback checkpoints
  • track blockers and record launch outcomes

Example prompts for the agent

  • Build an execution plan for the “Onboarding Refresh” initiative over 60 days, owned by marketing and product: /customer-journey-orchestration:implement-actions --initiative "Onboarding Refresh" --timeline 60d --owners "marketing,product"
  • Plan the “Signup Journey Update” through 2026-01-15, with product and ops owners and conversion KPIs: `/customer-journey-orchestration:implement-actions --initiative "Signup Journey Update" --timeline 2026-01-15 --owners "product,ops" --kpis "conversion"`

How to install implement-actions

Manually: put the files in place

.claude/commands/implement-actions.md

Call it with /implement-actions. For all projects use ~/.claude/commands/

Questions about implement-actions

How do I install implement-actions in Claude Code?

Save the command as .claude/commands/implement-actions.md.

What does implement-actions do?

It turns a prioritized journey initiative into a delivery plan with tasks, owners, dependencies, measurement, and launch tracking.

Where does implement-actions save its plan?

The plan JSON goes in .claude/plans/plan-<timestamp>.json, with task IDs, parallel groups, dependencies, error handling, and success metrics.

Source text

implement-actions.md · Apache-2.0
---
name: implement-actions
description: Converts prioritized journey initiatives into coordinated execution plans with measurement.
usage: /customer-journey-orchestration:implement-actions --initiative "Onboarding Refresh" --timeline 60d --owners "marketing,product"
---

# Command: implement-actions

## Inputs
- **initiative** – name of the prioritized journey program.
- **timeline** – duration or deadline (e.g., 60d, 2026-01-15).
- **owners** – comma-separated list of accountable teams.
- **budget** – optional resource or dollar allocation.
- **kpis** – optional key metrics to monitor.

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

- **Pattern selection**: Implementation runs **pipeline** (plan → workstreams → change mgmt → measurement → governance). If workstreams can execute in parallel, document a **diamond** segment with merge gate in the plan header.
- **Plan schema**: Save `.claude/plans/plan-<timestamp>.json` capturing initiative, timeline, task IDs, parallel groups, dependency graph (marketing, product, ops, enablement), error handling, and success metrics (KPI targets, VOC improvements).
- **Tool hooks**: Reference `docs/gtm-essentials.md` stack—Serena for instrumentation/config diffs, Context7 for SOPs, Sequential Thinking for retros, Playwright for experience QA if required.
- **Guardrails**: Default retry limit = 2 for blocked workstreams; escalation ladder = Journey Ops Owner → CX Strategist → CCO/Product leadership.
- **Review**: Run `docs/usage-guide.md#orchestration-best-practices-puerto-parity` before execution to confirm owners, dependencies, deliverables.

## Workflow
1. **Plan Assembly** – pull prioritized gap details, define scope, deliverables, and success metrics.
2. **Workstream Breakdown** – create task tree (content, product, ops, enablement) with owners + dependencies.
3. **Change Management** – map approvals, communications, enablement, and risk mitigation steps.
4. **Measurement Setup** – configure instrumentation, dashboards, VOC checkpoints, and cadence of reviews.
5. **Launch + Governance** – track execution status, surface blockers, and log outcomes for future journey reviews.

## Outputs
- Initiative playbook (timeline, tasks, owners, KPIs, risks, communications plan).
- Dashboard + tracker links for ongoing monitoring.
- Post-implementation recap capturing results and learnings.
- Plan JSON entry stored/updated in `.claude/plans` for audit trail.

## Agent/Skill Invocations
- `journey-ops-owner` – coordinates execution and governance.
- `governance` skill – ensures approvals + documentation.
- `voice-of-customer` skill – keeps measurement tied to customer feedback loops.

## GTM Agents Safeguards
- **Fallback agents**: document substitutes (e.g., CX Strategist covering Journey Ops Owner) if leads unavailable.
- **Escalation triggers**: if KPIs miss guardrails twice or blockers persist beyond SLA, escalate to CX/Product leadership per GTM Agents rip-cord.
- **Plan maintenance**: update plan JSON/change log whenever scope, owners, or measurement cadences change to maintain GTM Agents audit parity.

---

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

Similar slash commands

All slash commands for Agent setup: memory, context, orchestration →

From the same set224

The whole set →
define-events define-events creates an analytics instrumentation specification with event schemas, owners, and QA steps. Useful when aligning tracking plans across CDPs, product analytics, and warehouses. CX Codex +1 ★ 450repo stars define-profiles The define-profiles command maps audience profile schemas, data sources, and activation needs. Use it to plan personalization across selected channels. CX Codex +1 ★ 450repo stars optimize-nurture optimize-nurture is a Claude Code command that turns nurture metrics and test results into an optimization plan. It flags weak stages and assigns follow-up work with owners and due dates. CX Codex +1 ★ 450repo stars co-plan-campaign co-plan-campaign builds a structured co-marketing campaign brief covering joint messaging, target audiences, asset ownership, and governance rules. CX Codex +1 ★ 450repo stars prioritize-accounts The prioritize-accounts command ranks target accounts by composite intent score, identifies coverage gaps, and recommends plays for each segment. CX Codex +1 ★ 450repo stars configure-rewards configure-rewards orchestrates reward catalog setup, fulfillment workflows, and QA verification prior to a loyalty program launch. CX Codex +1 ★ 450repo stars configure-branches The configure-branches command for Claude Code generates step-by-step instructions for configuring branching, personalization, and automations in nurture campaigns. CX Codex +1 ★ 450repo stars run-standups run-standups runs a daily MQL→SQL pipeline standup, pulling routing metrics, logging blockers and assigning follow-up actions. CX Codex +1 ★ 450repo stars

Project sponsors

Companies that keep this analytics open