Menu
Generate a detailed handover message for continuing work in a new session. Use at end of session or when context window is getting long.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Dashboard of current GTM state across all active modules. Use when user asks about status, progress, or what to do next.
Upgrade this GTM Context OS instance to the latest template developments. Fetches the latest template, reconciles what's new against THIS instance's structure, and applies approved changes on a review branch — pausing before anything destructive. Operator-initiated.
Guided first-use setup. Walk through filling context.md and ingesting the first sales call. Use when the repo is empty or context.md is unfilled.
Smoke test before merging dev to main. Bootstraps a clean worktree, runs evals, checks instruction consistency — all automated via sub-agents.
First thing to run. Checks repo state and recommends what to do next. Use when operator says 'what do I do', 'help me get started', 'where do I begin', or just seems lost.
Audit the health of THIS instance's lived-in state — structural completeness, evidence chains, index integrity, output hygiene, drift, and context.md consistency (conflicts + cached-vs-source drift). Reports findings and fixes safe drift; flags judgment calls. Runs inside Claude Code, no API key.
| name | handover |
| description | Generate a detailed handover message for continuing work in a new session. Use at end of session or when context window is getting long. |
Generate a handover message that captures everything a fresh session needs to continue the current work.
Scans the current conversation and produces a structured handover message the user can paste into a new session. The message should give the new session full context without requiring it to re-read files or re-discover decisions.
Review the conversation and determine:
List every significant decision, with reasoning:
Format as a single message the user can paste. Structure:
## Handover: [project/task name]
### Context
[1-2 sentences: what this is, who it's for]
### What Was Done
[Bullet list of completed work with file paths]
### Key Decisions
[Numbered list of decisions with brief reasoning]
### Current State
[Where things stand right now — what's ready, what's draft, what's blocked]
### Open Items / Next Steps
[What the new session should pick up]
### Key Files
[File paths the new session will need to read]