AymAbdalla/gtm-engine

Ten GTM engineering skills for Claude Code and Codex, packaged as the aym-gtm plugin. They cover outbound from start to finish: who to sell to, which data is safe to use, who has a reason to hear from you now, who goes into a play, what to say, what to do today, how the book and the CRM stay in step, whether any of it works, and what to automate first.
Every skill reads and writes plain files (CSV, JSON, Markdown) in one workspace folder, and works with any CRM, sequencer or data vendor. Nothing sends a message, enrolls anyone or writes to a live system. A script does the checking and a person makes every decision that can't be undone.
Case study: how these skills were built, tested and fixed, with the evidence for each claim and its limits.
## Install
Claude Code:
/plugin marketplace add AymAbdalla/gtm-engine
/plugin install aym-gtm@gtm-engine
Codex:
codex plugin marketplace add AymAbdalla/gtm-engine
Then install aym-gtm from the Codex plugin list. Run a skill directly with /aym-gtm:daily-plan (Claude Code) or $daily-plan (Codex).
## The ten skills, in the order they run
| Skill | The question it answers |
| icp-define | Who should we sell to? Writes the ICP as testable rules and sorts every account in, out or unknown, with one reason each. |
| data-quality | Who on this list can we actually contact? Cleans a list into five buckets, verifies before outreach, audits a CRM export. |
| signal-score | Who has a real reason to hear from us now? Scores dated buying signals and writes one sourced why-now line per account. |
| account-book | What is the one record of every account and person? Merges sources, keeps your edits, gates each channel, picks one strategy per account. |
| play-build | Who goes into this play, and why? Proposes an enrollment list with every drop counted and explained. |
| outreach-draft | What do we say, and is it true? Drafts messages, then checks numbers, names, claims and the send gate, and holds anything it can't back for a person. |
| daily-plan | What do I do today, and did it all get done? Plans the day in each prospect's calling hours and closes it with nothing unlogged. |
| crm-sync | How do the book and the CRM stay in step? Compares both with their last agreed values and writes a plan a person applies. |
| funnel-review | Is any of this working, and how sure are we? Rates with counts and 95% ranges, pre-registered tests, at most three actions. |
| motion-map | What should we automate first? Checks a map of the sales motion and picks one step to move up one automation level. |
Each skill folder has a SKILL.md, reference files, its scripts and a made-up example workspace you can run.
## How the skills share one system
One ICP-fit rule (scripts/gtmfit.py), copied byte for byte into the four skills that judge fit, so an account can't fit in one step and fail in the next. A blank field means "enrich first", never "out".
Open deals flow from the CRM export through the account book to the play and the day plan, so outreach stops at any account with a live deal.