GTM OS — Weekly Index (CLAUDE.md)

# GTM OS — Weekly Index (CLAUDE.md) This skill owns CLAUDE.md — the index file that every GTM OS session reads first. It's written last (after the five foundation files exist) and updated most frequently. Think of it as the weekly briefing document that keeps Claude current without re-reading everything. ## What CLAUDE.md captures CLAUDE.md has one job: tell Claude what's happening RIGHT NOW so it doesn't give advice based on a snapshot from three months ago. It is never more than 50 lines. If it's longer, it's doing the wrong job. ### Section 1 — This week (5 lines max) - Current week and quarter - The one thing that matters most this week - Any live deals in a critical stage - Any campaigns active right now - Any context that would change how Claude should respond (board prep, comp change, product launch, etc.) ### Section 2 — Active campaigns (brief) For each active outbound or inbound campaign: - Campaign name and target segment - Current status (launched / running / pausing) - What's working, what isn't (one line each) - Next action ### Section 3 — Pointers to the other files Short references to where the deep context lives: - "Full ICP: see icp-definition.md" - "Competitive intel: see competitor-radar.md" - etc. This section exists so Claude knows where to go for depth. CLAUDE.md is the map, not the territory. ## The Monday ritual Every Monday morning, 5 minutes: 1. Update "This week" with the new date and reprioritize the one thing that matters. 2. Update campaign statuses — anything that launched, paused, or ended last week. 3. Remove anything from the file that's no longer live. 4. Add anything new that Claude needs to know right now. That's it. If it takes more than 5 minutes, the file has grown too large. Cut it back. ## How to build the first version Ask the user: "What's the most important thing happening in your GTM motion right now — this week, not this quarter?" Then: "What campaigns are actively running? What's the status of each?" Then: "Is there anything unusual happening right now that would change how I should help you — a board meeting, a comp change, a product launch, a reorg?" Write the first CLAUDE.md together. Keep it under 30 lines for the first version — it's easier to add than to cut. ## Anti-patterns to flag - CLAUDE.md longer than 50 lines — it's an index, not a document. Cut it down. - "This week" section that hasn't been updated in 7+ days — it's lying to Claude. Update or archive. - No pointers to the other files — without them, Claude won't know where to look for depth. - Campaign statuses that are vague ("running well") — push for specific metrics or observations. - A CLAUDE.md written before the five foundation files exist — build those first.