Learn GitHub and run your GTM on a repo
GitHub is the hidden prerequisite for AI-native GTM. If you cannot manage a repo, you cannot run a context brain, install skills, or keep your GTM system in one place. Most operators learn this the hard way.
Learn GitHub and run your GTM on a repo
GitHub is the hidden prerequisite for AI-native GTM.
If you cannot manage a repo, you cannot run a context brain, install skills, or keep your GTM system in one place. Most operators learn this the hard way.
GitHub literacy the operator way
A private repo you run your GTM from
The habits that keep it clean
The governance file
The same GitHub-for-GTM discipline: commit, push, and keep the rules that make a repo reliable.
The teams pulling ahead run their GTM from a repo. If GitHub is a black box, you are locked out of the whole motion: no context brain, no installed skills, no single source of truth. And you learn it the hard way, on YouTube at 11pm, like the rest of us did.
The workflow that solves it, one step at a time.
Each step is the plain question you are already asking. The skills answer them in order, one handing its receipt to the next.
The operator version of git: the mental model (repo, commit, branch, push, pull), a GUI-first workflow so you never fear the terminal, how to organize the repo, and the hard rules on what to never commit. The prerequisite nobody teaches GTM.
A proposed naming convention, folder structure, index, and cleanup plan, shown as a plan first so you see every move.
A single pack that tells a new session or teammate what the project is, where things live, what's decided, and the next move.
A running log where each entry captures the decision, the context, the options, the why, and when to revisit.
Verifies every change is committed, pushed, and green, confirms it is live, updates the notes, and hands back a summary with a rollback path.
GitHub literacy the operator way, a private repo you run your GTM from, and the habits that keep it clean.
- All 5 chained skills resolve to real, scored skills.
- Has a problem, an outcome, 2+ steps, and proof from a real build.
- Ships an example chat showing the play run in Claude.
- Reads in plain operator voice, grounded in a real build.
We did not just check the structure. A judge read this play against the full text of every skill it chains (composition), then ran it on a real scenario end to end (simulated). It passed both. Test scenario: Dana, a RevOps lead who has never used GitHub and finds it intimidating, wants to put her GTM in a repo.
Watch the skills answer in order.
Describe your situation in plain language. The right skill fires on its own and hands its receipt to the next.
Before you run it, I ran it for real.
This workflow is genericized from a real build. Here is the number it moved, and what I actually did.
WHAT I DID ›
When you automate, your failures go silent. Write them down as enforced gates, not documentation. A governance file that reads your own failure history is how a pipeline stops repeating its worst week.
Dig into the full build →One plugin. 5 skills, bundled.
The whole playbook installs as a single plugin in Claude Code, no copy-pasting 5 times. Or grab any single step above. It runs on what you paste; connect your stack to go live.