ctx-check

Name: ctx-check
Availability: InStock
Author: mikecubed

Verify .agent/SESSION.md presence and freshness before non-trivial work.

Updated Mar 18, 2026

Search Tags:#workflow #context #validation #hygiene #conductor #session

Ready to run

npx skills add https://github.com/mikecubed/agent-orchestration --skill ctx-check

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ctx-check
Source: https://github.com/mikecubed/agent-orchestration/tree/main/plugins/ccc/skills/ctx-check
Command: npx skills add https://github.com/mikecubed/agent-orchestration --skill ctx-check

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Context hygiene enforcement across the conductor workflow to prevent proceeding with stale or missing session state, exceeded failed-hypothesis budgets, and missing codebase briefs before non-trivial implementation tasks.

Core Features & Use Cases

CTX-1 — Stale or Absent SESSION.md detection with warnings and guidance integrated into the conductor's flow.
CTX-2 — Failed-Hypothesis budget monitoring with warnings to consolidate state before creating new hypotheses.
CTX-3 — Missing codebase briefs detection for non-trivial tasks, prompting a scout pass or discovery summary.

Quick Start

Run a session hygiene check before starting non-trivial work to ensure a valid and current session context.

Frequently Asked Questions about ctx-check

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

FAQPage Schema

How do I check for stale or missing session context before starting development work?▼

Failed-hypothesis budget monitoring tracks exceeded hypothesis limits during multi-step development, warning you to consolidate state before creating new hypotheses. This prevents unfocused implementation when prior assumptions have failed.

How do I detect missing codebase briefs for non-trivial development tasks?▼

Missing codebase brief detection prompts a scout pass or discovery summary when non-trivial tasks lack required context. This enforces proper discovery before allowing implementation work to proceed within the conductor workflow.

When should I require a HANDOFF.json confirmation during multi-step development?▼

HANDOFF.json satisfaction is required when session state needs explicit boundary confirmation before proceeding. This verification triggers during write and review operations when context freshness or task boundaries are ambiguous.

Does session context validation work without external dependencies?▼

Session context validation operates with zero external dependencies, relying solely on .agent/SESSION.md file inspection and timestamp checks. This enables workflow enforcement in any development environment without package installations.