Initial commit

commands/implement-actions.md

@@ -0,0 +1,48 @@
+---
+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.
+
+---

commands/map-journey.md

@@ -0,0 +1,48 @@
+---
+name: map-journey
+description: Facilitates end-to-end journey mapping workshops with data-backed insights and ownership plans.
+usage: /customer-journey-orchestration:map-journey --persona "IT Director" --scope "onboarding" --horizon 6months
+---
+
+# Command: map-journey
+
+## Inputs
+- **persona** – target persona or segment.
+- **scope** – journey slice (awareness, onboarding, adoption, renewal, expansion).
+- **horizon** – time window to analyze (e.g., 6months, lifecycle).
+- **data_sources** – optional list of VOC/telemetry sources to emphasize.
+- **facilitators** – optional list of stakeholders joining workshops.
+
+### GTM Agents Pattern & Plan Checklist
+> Based on GTM Agents orchestrator blueprint @puerto/plugins/orchestrator/README.md#112-325.
+
+- **Pattern selection**: Journey mapping typically runs **pipeline** (discovery → workshop → evidence → gaps → synthesis). If workshop activities can split (e.g., persona + channel subgroups), log a **diamond** segment with merge gate in the plan header.
+- **Plan schema**: Save `.claude/plans/plan-<timestamp>.json` capturing persona, scope, task IDs, parallel groups, dependency graph (research, CX ops, product), error handling, and success metrics (gap closure %, NPS uplift, time-to-resolution).
+- **Tool hooks**: Reference `docs/gtm-essentials.md` stack—Serena for instrumentation diffs, Context7 for VOC/support docs, Sequential Thinking for facilitation prompts, Playwright for QA on journey prototypes if needed.
+- **Guardrails**: Default retry limit = 2 for evidence gaps or facilitation blockers; escalation ladder = CX Strategist → Journey Ops Owner → CCO/CS leadership.
+- **Review**: Run `docs/usage-guide.md#orchestration-best-practices-puerto-parity` before execution to confirm facilitators, dependencies, and deliverables.
+
+## Workflow
+1. **Discovery Packet** – compile research, telemetry, and existing maps for the selected persona/scope.
+2. **Workshop Flow** – guide stakeholders through stage definition, touchpoint inventory, emotion mapping, and ownership assignment.
+3. **Evidence Layer** – inject VOC quotes, product metrics, and support data to ground decisions.
+4. **Gap Logging** – capture friction points, root causes, and potential solutions.
+5. **Synthesis** – produce journey blueprint, highlight quick wins, and queue items for prioritization.
+
+## Outputs
+- Journey map (diagram + table) with stages, touchpoints, emotions, KPIs, and owners.
+- Gap log referencing supporting data and potential solutions.
+- Stakeholder recap with action items and next steps.
+- Plan JSON entry stored/updated in `.claude/plans` for audit trail.
+
+## Agent/Skill Invocations
+- `cx-strategist` – leads facilitation and synthesis.
+- `journey-mapping` skill – provides templates/checklists.
+- `research-lead` – injects VOC evidence.
+
+## GTM Agents Safeguards
+- **Fallback agents**: document substitutes (e.g., Journey Ops Owner covering CX Strategist) when facilitators unavailable.
+- **Escalation triggers**: if critical gaps lack owners after two checkpoints or evidence quality falls below guardrails, escalate to CX + Product leadership per GTM Agents rip-cord.
+- **Plan maintenance**: update plan JSON/change log when scope, facilitators, or data sources change to keep audit alignment with GTM Agents procedures.
+
+---

commands/prioritize-gaps.md

@@ -0,0 +1,48 @@
+---
+name: prioritize-gaps
+description: Scores journey friction points, aligns owners, and builds remediation roadmap.
+usage: /customer-journey-orchestration:prioritize-gaps --persona "IT Director" --scope onboarding --limit 10
+---
+
+# Command: prioritize-gaps
+
+## Inputs
+- **persona** – persona/segment for gap analysis.
+- **scope** – journey stage or lifecycle slice.
+- **limit** – optional cap on number of gaps to surface.
+- **criteria** – optional weighting scheme (impact, effort, urgency, customer value).
+- **dependencies** – optional notes about systems/teams involved.
+
+### GTM Agents Pattern & Plan Checklist
+> Mirrors GTM Agents orchestrator blueprint @puerto/plugins/orchestrator/README.md#112-325.
+
+- **Pattern selection**: Gap prioritization generally runs **pipeline** (aggregation → scoring → owner mapping → roadmap → comms). If scoring + owner mapping can run in parallel (multiple pods), document a **diamond** segment with merge gate in the plan header.
+- **Plan schema**: Save `.claude/plans/plan-<timestamp>.json` with persona/scope, task IDs, weighting criteria, parallel groups, dependency graph (ops, product, eng), error handling, and success metrics (gap closure %, CSAT uplift, time-to-fix).
+- **Tool hooks**: Reference `docs/gtm-essentials.md` stack—Serena for instrumentation diffs, Context7 for VOC/support docs, Sequential Thinking for decision tree prompts, Playwright for QA on prototype fixes if required.
+- **Guardrails**: Default retry limit = 2 for scoring/owner mapping failures; escalation path = Journey Ops Owner → CX Strategist → CCO/CS leadership.
+- **Review**: Use `docs/usage-guide.md#orchestration-best-practices-puerto-parity` before execution to confirm facilitators, data sources, and deliverables.
+
+## Workflow
+1. **Gap Aggregation** – pull journey map findings, VOC insights, support tickets, and telemetry anomalies.
+2. **Scoring Engine** – apply weighting (impact × frequency × effort × strategic fit) to rank opportunities.
+3. **Owner Mapping** – assign accountable teams, supporting partners, and required approvals.
+4. **Roadmap Packaging** – cluster into quick wins, strategic bets, and structural fixes with timelines.
+5. **Communication Plan** – generate summary for executives + working teams with next steps.
+
+## Outputs
+- Prioritized gap list with scores, owners, and proposed actions.
+- Portfolio view (quick wins vs strategic initiatives) with resource estimates.
+- Governance-ready backlog entry for each initiative.
+- Plan JSON entry stored/updated in `.claude/plans` for audit trail.
+
+## Agent/Skill Invocations
+- `journey-ops-owner` – coordinates resourcing + timelines.
+- `journey-mapping` skill – ensures gap definitions align with map standards.
+- `voice-of-customer` skill – keeps scoring grounded in customer evidence.
+
+## GTM Agents Safeguards
+- **Fallback agents**: document substitutes (e.g., CX Strategist covering Journey Ops Owner) when resource owners unavailable.
+- **Escalation triggers**: if high-impact gaps remain unassigned after two checkpoints or portfolio balance violates guardrails, escalate to CX/Product leadership per GTM Agents rip-cord.
+- **Plan maintenance**: update plan JSON/change log whenever scoring criteria, owners, or dependencies change to maintain GTM Agents audit parity.
+
+---