Part of Run Go-to-Market Operations With AI Context
Marketing Blueprint
Safety checkedKeep GTM Context Current Weekly
Identify stale context sections, draft updates, and refresh your knowledge base without manual rebuilding.
What problem does this solve?
Automatically diffs your repo to find stale context (outdated priorities, inactive campaign results, old competitor intel), drafts updates based on what it can infer from your outputs, and asks focused questions for the rest. This keeps your context library current in 10-15 minutes instead of 45 minutes of manual rebuilding.
How does it work?
Run weekly-update on Monday mornings. 1. Claude reads CLAUDE.md, signal library, ICP definition, and all outputs from the last 14 days to identify what's stale. 2. For each stale section (outdated priorities, inactive campaign results, inactive signals), Claude drafts a proposed update based on current repo state. 3. Claude asks you focused questions for information it can't infer (updated ACV, new competitive patterns, signal performance from live campaigns). 4. You confirm; Claude applies updates to all affected files and logs the change. Output: all context files stay current with minimal manual input.
Included Skills
No skills in this group
What's required to run this?
Runs on your existing files with no external dependencies. If you've configured the sync scripts (sync-campaign-results.py, sync-signal-performance.py), run those first to pull live metrics from your outbound tool and CRM; the weekly-update skill will incorporate that data automatically. Optional: OpenClaw can automate this entire workflow on a schedule (pull metrics, run update skill, send Slack summary).
Key Features
Staleness detection
Flags priorities not updated in 7 days, campaign results not updated in 7 days, competitor radar not updated in 60 days, ICP not updated in 90 days.
Focused questions
Only asks about things Claude can't know. Your actual campaign metrics, new competitive patterns, strategy shifts. No busy-work.
Drafted updates
Shows CURRENT vs. PROPOSED for each stale section so you can review before confirming.
Signal performance tracking
Pulls metrics from active campaigns and updates your signal-library performance log with reply rates and meeting rates by signal.
Change log
Writes a one-line entry to outputs/weekly-log.md with date and what changed, so you can track repo evolution over time.
About This Blueprint
- Industry
- Technology
More Blueprints to explore
Find, rank, and enrich prospects your partners already sell to with AI
Your warmest prospects are the ones already buying from your partners. Find each one with the right contact and a reason to reach out, so your team stops splitting their time across a cold list.
Automated Data Pipeline for Reliable Data Processing and Business Insights
Avoid inconsistent business reports by validating data quality before transformed records reach analytics and reporting systems. Ongoing pipeline monitoring helps teams catch processing problems before they undermine business insights.
Harikrishnan K.
Data Engineer at Decision Minds