gtm-icp-refresh

Featured

Monthly, on the last weekday. Re-tests every segment in strategy/icp.md against the evidence in this kit's own ledgers, then rewrites the targeting itself where the evidence disagrees with the assumption the segment was written on. It records every change in strategy/CHANGELOG.md. It sends only where you released the channel, never re-queues anyone, never edits the contacted ledger, and never writes a number it did not read out of a named file.

AI & Automation 432 stars 135 forks Updated today MIT

Install

View on GitHub

Quality Score: 94/100

Stars 20%
88
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# ICP refresh **Run the guard before you read anything else, this file included past this line.** Through `shell.run`: `node "«GTM_ROOT»/scripts/guard.mjs" gtm-icp-refresh`. It reads `PAUSED`, your row in `SCHEDULE.md`, and `state/gtm-icp-refresh.json`, and prints one verdict. On `skipped-paused`, `skipped-out-of-window`, `skipped-already-ran`, or `failed` it has already appended the run record: exit now and read nothing else. On `run`, carry on. Step 0 below repeats the same checks by hand and they stay, because a harness with no `shell.run` has nothing else to run them with; the guard exists so that a fire that should not run costs cents instead of a full read of the contract. You are the targeting analyst for this business. Once a month you answer the one question the weekly scoreboard never asks: are we still aiming at the right people at all. **The deliverable is `strategy/icp.md` as it stands when you finish**, plus the lines in `strategy/CHANGELOG.md` that say what moved and what moved it. The evidence table is how you get there, not what you hand over. An evidence table nobody acted on is half a run, and a rewrite with no ledger path beside it is an opinion. Read `«GTM_ROOT»/CONTRACT.md` first, every run, including its `## Corrections` section. It is the spine. Where anything below and the contract disagree, the contract wins. Where the contract and the member's own workspace rule file disagree, the member's file wins. Read the `## Corrections` at the bottom of th...

Details

Author
markfulton
Repository
markfulton/ai-employees
Created
3 weeks ago
Last Updated
today
Language
JavaScript
License
MIT

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Featured

csat-taxonomy-refresh

Monthly on the last weekday, light browser lane. Re-tests every theme and every severity rule against a month of real ticket evidence and rewrites strategy/themes.md wherever the evidence disagrees with the assumption. It merges two themes the evidence shows are one, splits a theme whose tickets have two different answers, retires a theme with no volume, creates a theme for a cluster that kept landing unclassified, and rewrites a severity rule wherever the outcomes contradict it. Theme ids are never reused and never renumbered. It holds every outbound action unless you released the channel, and it never touches a credential.

432 Updated today
markfulton
AI & Automation Featured

gtm-intake-and-dashboard

Runs once by hand on the first day and once a month after that. On the first run it researches the business from its own public surfaces before asking anything, writes the strategy folder, seeds the launch board, builds the tailored command center, reconciles the schedule table, and registers the recurring jobs. On every monthly run it re-reads the evidence the kit produced, applies what changed, reconciles drift, and rebuilds. It holds every outbound action unless you released the channel, and it never enters a credential.

432 Updated today
markfulton
AI & Automation Featured

sales-qualification-refresh

Monthly, on the last weekday, light browser lane. Re-tests every named qualification test and every buyer segment against a month of this kit's own ledger evidence, then rewrites both files itself where the evidence disagrees with the assumption they were written on. It records every change in strategy/CHANGELOG.md with the ledger path that justified it. It sends only where you released the channel, never re-queues anyone, never edits the contacted ledger, and never writes a number it did not count out of a named file.

432 Updated today
markfulton