Initial commit
This commit is contained in:
33
commands/monitor-abm.md
Normal file
33
commands/monitor-abm.md
Normal file
@@ -0,0 +1,33 @@
|
||||
---
|
||||
name: monitor-abm
|
||||
description: Builds an ABM operations dashboard + action plan for engagement, pipeline, and experiment tracking.
|
||||
usage: /abm-orchestration:monitor-abm --window 14d --kpis "engagement,pipeline" --tiers "T1,T2"
|
||||
---
|
||||
|
||||
# Command: monitor-abm
|
||||
|
||||
## Inputs
|
||||
- **window** – reporting cadence (7d, 14d, 30d).
|
||||
- **kpis** – comma-separated metrics (engagement, meetings, pipeline, win rate, velocity).
|
||||
- **tiers** – tiers to highlight.
|
||||
- **experiments** – optional test IDs or hypotheses to report on.
|
||||
- **alerts** – optional thresholds for notifications.
|
||||
|
||||
## Workflow
|
||||
1. **Data Consolidation** – CRM, MAP, ads, web analytics, SDR activity, events.
|
||||
2. **KPI Visualization** – build charts/tables by tier, persona, channel, play.
|
||||
3. **Insight & Action** – detect drop-offs, accounts needing intervention, creative fatigue.
|
||||
4. **Experiment Review** – summarize running tests, significance, next steps.
|
||||
5. **Governance** – document owner assignments, follow-ups, escalation paths.
|
||||
|
||||
## Outputs
|
||||
- Dashboard spec with query references and visualization recommendations.
|
||||
- Weekly digest framework (insights, actions, blocked items).
|
||||
- Alert + SLA tracker for tiered escalations.
|
||||
|
||||
## Agent/Skill Invocations
|
||||
- `abm-analyst` – drives data synthesis.
|
||||
- `signal-intel` skill – ensures intent/product signals surface in reporting.
|
||||
- `account-tiering` skill – keeps metrics aligned to tier definitions.
|
||||
|
||||
---
|
||||
48
commands/plan-plays.md
Normal file
48
commands/plan-plays.md
Normal file
@@ -0,0 +1,48 @@
|
||||
---
|
||||
name: plan-plays
|
||||
description: Produces an ABM playbook roadmap with offers, channels, and timelines aligned to tiers.
|
||||
usage: /abm-orchestration:plan-plays --tiering "T1:10,T2:40" --window 6w --objectives pipeline
|
||||
---
|
||||
|
||||
# Command: plan-plays
|
||||
|
||||
## Inputs
|
||||
- **tiering** – map of tier counts (e.g., `T1:10,T2:40`).
|
||||
- **window** – program duration (e.g., 6w, quarter).
|
||||
- **objectives** – pipeline, expansion, strategic meetings, adoption.
|
||||
- **channels** – optional list (ads, email, direct mail, exec events, social).
|
||||
- **offers** – optional predefined offers to include.
|
||||
|
||||
### GTM Agents Pattern & Plan Checklist
|
||||
> Derived from GTM Agents orchestrator model @puerto/plugins/orchestrator/README.md#112-325.
|
||||
|
||||
- **Pattern selection**: Start with a **diamond** pattern (strategy intake → parallel pod planning → consolidation) and switch to **pipeline** when play development must stay sequential. Record the chosen pattern in the plan header.
|
||||
- **Plan schema**: Every run saves `.claude/plans/plan-<timestamp>.json` including objective, stages, parallel groups, agent assignments, context handoffs, error handling, and success criteria.
|
||||
- **Tool hooks**: Reference `docs/gtm-essentials.md` tools explicitly (Serena for CRM/MAP patches, Context7 for platform docs, Sequential Thinking for retros, Playwright for QA on assets/landing pages).
|
||||
- **Guardrails**: Define retry strategy (default 2 attempts) and escalation path (ABM Strategist → Sales Director) for any failed stage.
|
||||
- **Review**: Before execution, run the checklist in `docs/usage-guide.md#orchestration-best-practices-puerto-parity` to confirm agents, dependencies, and deliverables.
|
||||
|
||||
## Workflow
|
||||
1. **Strategy Alignment** – confirm goals, budget, team capacity, channel constraints.
|
||||
2. **Play Library Selection** – choose plays per tier (executive experience, custom content, direct mail, workshops, ads).
|
||||
3. **Timeline & Cadence** – schedule waves of outreach, follow-up, and standups.
|
||||
4. **Asset & Owner Mapping** – identify required content, personalization, approvals, stakeholders.
|
||||
5. **Measurement Plan** – define KPIs per play (engagement, meetings, pipeline) and reporting cadence.
|
||||
|
||||
## Outputs
|
||||
- Playbook table (tier, play, channel, owner, CTA, assets, SLAs).
|
||||
- Calendar/timeline highlighting waves, reviews, retros.
|
||||
- Risk + dependency log (asset gaps, approval needs, data requirements).
|
||||
- Plan JSON stored in `.claude/plans` with version history (update if owners/scope change).
|
||||
|
||||
## Agent/Skill Invocations
|
||||
- `abm-strategist` – leads play selection + governance.
|
||||
- `account-planner` – maps plays to specific accounts/personas.
|
||||
- `personalization` skill – ensures messaging + assets are tailored.
|
||||
|
||||
## GTM Agents Safeguards
|
||||
- **Fallback agents**: document substitutions (e.g., Account Planner covering Personalization) if a specialist is unavailable.
|
||||
- **Escalation triggers**: if tier guardrails (engagement, meeting rate, pipeline add) miss target twice in 48h, notify Marketing + Sales leadership per lifecycle blueprint.
|
||||
- **Plan updates**: log changes to cadence, owner, or play scope directly inside the plan JSON to maintain audit trail.
|
||||
|
||||
---
|
||||
33
commands/target-accounts.md
Normal file
33
commands/target-accounts.md
Normal file
@@ -0,0 +1,33 @@
|
||||
---
|
||||
name: target-accounts
|
||||
description: Generates a prioritized ABM target list with tiering, buying committees, and activation triggers.
|
||||
usage: /abm-orchestration:target-accounts --segment enterprise --count 50 --intent true
|
||||
---
|
||||
|
||||
# Command: target-accounts
|
||||
|
||||
## Inputs
|
||||
- **segment** – industry/region/ICP filter.
|
||||
- **count** – number of accounts to return per tier.
|
||||
- **intent** – whether to pull live intent signals (true/false).
|
||||
- **customers** – include/exclude customers for expansion plays.
|
||||
- **notes** – optional constraints (ex: “no active opps”).
|
||||
|
||||
## Workflow
|
||||
1. **Data Merge** – combine CRM, enrichment, intent, product usage, partner data.
|
||||
2. **Scoring & Tiering** – apply ideal customer fit, engagement, pipeline stage to produce T1/T2/T3 split.
|
||||
3. **Buying Committee Mapping** – surface key personas, roles, known contacts.
|
||||
4. **Signal Highlights** – list recent intent spikes, product usage, news, hiring signals.
|
||||
5. **Activation Suggestions** – propose first-touch plays per tier.
|
||||
|
||||
## Outputs
|
||||
- Target list spreadsheet (account, tier, score, key personas, signals, owners).
|
||||
- Buying committee summary + contact gaps.
|
||||
- Recommended next play per tier (event invite, executive briefing, nurture).
|
||||
|
||||
## Agent/Skill Invocations
|
||||
- `abm-strategist` – ensures scoring logic aligns with program goals.
|
||||
- `account-tiering` skill – enforces tier definitions.
|
||||
- `signal-intel` skill – aggregates intent/product signals.
|
||||
|
||||
---
|
||||
Reference in New Issue
Block a user