Build your operator system
Every session starts cold and nothing you learn sticks. Give your work memory and a closed loop. Already run run-your-gtm-on-github? You already have context-pack, decision-log, and session-closeout, skip to runbook-builder and closed-loop.
Build your operator system
Every session starts cold and nothing you learn sticks.
Give your work memory and a closed loop. Already run run-your-gtm-on-github? You already have context-pack, decision-log, and session-closeout, skip to runbook-builder and closed-loop.
Details
Details
Details
Details
Details
The 7th analyst
The meta-analyst and closed loop that make a system compound.
A context pack
A decision log
Runbooks
A safe closeout
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.
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.
A step-by-step SOP for a repeated process, who does what, when, and how, with named failure points and a check on every step.
Verifies every change is committed, pushed, and green, confirms it is live, updates the notes, and hands back a summary with a rollback path.
Scans a session for corrections, approvals, and validated patterns, then proposes exact edits to your skills and docs. Nothing applied until you approve.
A context pack, a decision log, runbooks, a safe closeout, and a system that improves itself.
- 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: Morgan, a RevOps operator, is tired of cold-starting every session and wants memory plus a closed loop.
This play runs across the org, not inside sales.
Every function below owns a piece of the play. Skip one and it stalls where most GTM plays stall: in the handoff.
Without it: The pack and the CRM tell two different stories.
Without it: The loudest voice in the room overrules the log.
Without it: Every output drifts back to last year's story.
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 ›
AI-native is not how many agents you have. It is whether one of them watches the others and turns their mistakes into improvements. Build the analyst that reads the audit trail. That is the one that compounds.
Dig into the full build →A system is only as good as what it learns
The skills hand you a context pack, a decision log, runbooks, and a closed loop; the compounding comes from the operator who feeds corrections back instead of just fixing them in place. Here is how a GTM leader turns a personal setup into a team system that gets sharper every week.
Every time an output gets fixed by hand, the fix gets thirty seconds of triage: one-off, or pattern. Patterns go through closed-loop into the runbook or the context pack the same day, and the weekly review checks for fixes that skipped triage.
- 01Train the write-it-down reflex
Teach the team what belongs in the decision-log versus a runbook versus the context pack, using real examples from their own week. A system nobody knows how to feed starves.
- 02Refresh the context pack on a clock
The pack goes stale silently. Tie the refresh to real events on a recurring date: a new hire, a positioning change, a quarter close.
- 03Runbook the workflow you repeat
When the same task shows up a third time, it earns a runbook-builder pass. The bar is that a new teammate could run it cold.
- 04Review the loop weekly
Once a week, read what closed-loop captured and what it changed. An empty week means corrections are leaking, not that the system is perfect.
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.