Gtm Icp Refresh
Monthly, on the last weekday.
Install
npx skills add markfulton/ai-employees --skill gtm-icp-refresh -g -a claude-code -y- Repository
- markfulton/ai-employees826
- Category
- Testing
- Updated
- 6d ago
- License
- MIT
- Context cost
- Mediumabout 3,000 tokens
- Runs scripts
- No, instructions only
What it does
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.
Shared work cycle
After the guard returns run, read WORK-CYCLE.md and your entry in work-profile.json. Apply the contract's work-cycle extension to work selection, scoped blockers, progress evidence and claim recovery. Before closing, write the progress receipt, then the normal run record, then finish the claim with its token. Preserve the remaining budget on a resume. A same-period run with a claim overrides only the legacy Step 0.2 exit/reset. All pause, release and browser guards still apply.
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.
