plan-plays — Claude Code command: what it does, how to install
plan-plays builds an ABM playbook roadmap across account tiers, mapping plays, channels and timelines to a chosen campaign objective.
Apache-2.0 ★ 450 updated 2026-04-03
.claude/commands/plan-plays.mdWhat plan-plays does
The /abm-orchestration:plan-plays command takes tier counts (like T1:10,T2:40), a program window (6w or a quarter) and an objective — pipeline, expansion, strategic meetings or adoption. It runs through five stages: aligning on goals, budget and team capacity; picking plays per tier from executive experiences, custom content, direct mail, workshops and ads; scheduling outreach and follow-up waves; mapping assets, personalization and approvals to owners; and setting KPIs per play with a reporting cadence.
The output is a playbook table (tier, play, channel, owner, CTA, assets, SLAs), a wave/review calendar, and a log of risks and dependencies such as missing assets or pending approvals. Each run writes the plan to .claude/plans/plan-<timestamp>.json, including the orchestration pattern picked (diamond or pipeline), stages, parallel groups and success criteria; any later change to owners or play scope gets logged there too.
Execution pulls in the abm-strategist sub-agent for play selection and governance, account-planner for mapping plays to specific accounts and personas, and the personalization skill for tailoring messaging and assets. Failed stages default to two retries before escalating from the ABM Strategist to the Sales Director.
What it helps with
- draft an account-tiered ABM playbook with plays and channels
- schedule outreach waves and follow-ups against a budget window
- assign owners, assets and SLAs to each play
- set up a KPI and reporting plan across an ABM program
- track risks and dependencies like missing approvals or assets
Example prompts for the agent
- /abm-orchestration:plan-plays --tiering "T1:10,T2:40" --window 6w --objectives pipeline
- Build a plan-plays roadmap for a quarter targeting strategic meetings across ads, email and direct mail
- Run plan-plays for tiers T1:5,T2:20 over a 6w window focused on adoption
How to install plan-plays
Manually: put the files in place
.claude/commands/plan-plays.mdCall it with /plan-plays. For all projects use ~/.claude/commands/
Manually: put the files in place
~/.codex/prompts/plan-plays.mdCall it with /prompts:plan-plays. Codex marks this format deprecated in favour of skills
Manually: put the files in place
.github/prompts/plan-plays.prompt.mdManually: put the files in place
.gemini/commands/plan-plays.tomlGemini stores commands as TOML: the prompt text goes into the prompt field
Questions about plan-plays
How do I install plan-plays in Claude Code?
Place the command file at .claude/commands/plan-plays.md in your project.
What does plan-plays do?
It builds an ABM playbook mapping plays, channels, timelines and owners to account tiers and a stated campaign objective, saving the plan as JSON.
Which sub-agents or skills does plan-plays call?
Play selection and governance go through the abm-strategist sub-agent, account/persona mapping through account-planner, and messaging tailoring through the personalization skill.
Source text
plan-plays.md · Apache-2.0
--- 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. ---
© gtmagents · Apache-2.0 · gtmagents/gtm-agents