meta-context-watcher

Writes session handover files and maintains a ranked standing backlog before context limits degrade quality.

1|Updated Jun 23, 2026
One-click install
npx skills add https://github.com/bitranox/bitranox-skills --skill meta-context-watcher-bitranox
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: meta-context-watcher
Source: https://github.com/bitranox/bitranox-skills/tree/main/plugins/bitranox/skills/meta-context-watcher
Command: npx skills add https://github.com/bitranox/bitranox-skills --skill meta-context-watcher-bitranox

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Long Claude Code sessions degrade in accuracy well before the context window fills, and auto-compaction discards working detail. This Skill preserves task state by writing a deliberate handover document and maintaining a persistent backlog so unfinished work and unmet user requests survive across sessions. ## Core Features & Use Cases - Session Handover Writing: Produces a handover.md capturing only what the next session cannot re-derive: in-flight work, uncommitted changes, decisions with reasons, and the exact next action. - Standing Backlog Management: Maintains OPEN-WORK.md, a ranked one-line-per-item backlog with origin (USER/FOUND), size, and first-raised dates, reconciled before every handover overwrite. - Automatic Threshold Detection: A Stop hook measures real token usage from the transcript and nudges a handover when context crosses a configurable threshold, with model-family window detection. - Use Case: A session approaches its context limit mid-refactor. The Skill reconciles open items into the backlog, writes a fresh handover with the next action, and instructs the user to type /clear so the next session resumes cleanly. ## Quick Start Ask Claude to write a handover for the current session and update the open-work backlog before starting a fresh session.

Frequently Asked Questions about meta-context-watcher

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I hand over a Claude Code session before context runs out?▼

Invoke the context-watcher skill to write a handover.md file capturing in-flight work, uncommitted changes, decisions, and the exact next action. It then instructs you to type /clear so the next session starts fresh with full context.

What is the difference between handover.md and OPEN-WORK.md?▼

handover.md describes one moment and is overwritten wholesale each session, while OPEN-WORK.md is a standing backlog edited line by line. The handover holds current task state; the backlog holds everything unfinished that outlives the session.

When does the context watcher hook trigger automatically?▼

A Stop hook measures real token usage from the transcript's last recorded usage and fires when context crosses min(context_handover_pct of the window, context_handover_cap). The window is detected from the model family, falling back to a declared or 200k window.

How are items ranked in the OPEN-WORK.md backlog?▼

User-requested items always outrank found items, deferred user items sit below live user items but above found ones, and larger size breaks ties within the same origin. Ranks use tens (10, 20, 30) so insertions avoid renumbering.

Why should I not keep working after writing the handover?▼

Any edit made after the handover is work the handover does not describe, so the next session inherits a file that is already wrong about the state it reports. The handover must be the last action, followed only by the /clear instruction.

Can the context window be configured manually?▼

Yes, set context_window explicitly via the meta-memory-settings skill if the watcher reports measuring more context than the window. Otherwise detection follows model family first, then the launcher's declared window, then a 200k fallback.