context-manager

Generate BOOT_CONTEXT.md, DELTA_CONTEXT.md, FEATURES/, and MANIFEST.json artifacts for stateless agents.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/yousufjoyian/claude-skills --skill context-manager-yousufjoyian
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: context-manager
Source: https://github.com/yousufjoyian/claude-skills/tree/main/context-manager
Command: npx skills add https://github.com/yousufjoyian/claude-skills --skill context-manager-yousufjoyian

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The context-manager skill generates compact, portable context artifacts to bootstrap stateless agents across multi-agent workflows, enabling fast, knowledge-rich spawns without re-reading the entire repository.

Core Features & Use Cases

  • BOOT_CONTEXT.md: a stable project brain used to initialize new agents with minimal token load.
  • DELTA_CONTEXT.md: captures recent changes to keep agents up-to-date with low overhead.
  • FEATURE BUNDLES: per-feature context slices under .claude/compiled/FEATURES for parallel tasks.
  • MANIFEST.json and FEATURE_MAP.yaml: provenance and task mappings that ensure deterministic rehydration.
  • Use cases: onboarding new agents, setting up multi-agent pipelines, and token-efficient knowledge transfer.

Quick Start

cms compile cms update

Frequently Asked Questions about context-manager

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

FAQPage Schema
How do I onboard stateless agents to a project without high token usage?

To onboard stateless agents without high token usage, generate compact, portable context artifacts like a BOOT_CONTEXT.md file that initializes new agents with minimal token load. This provides a stable project brain for fast, knowledge-rich spawns.

What is the best way to share context across multi-agent workflows?

The best way to share context across multi-agent workflows is to enforce deterministic outputs via MANIFEST.json and FEATURE_MAP.yaml. These provide provenance and task mappings that ensure reliable rehydration for parallel tasks.

How do I generate context artifacts for parallel feature tasks?

Generate context artifacts for parallel tasks by running `cms compile` to create per-feature context slices under a compiled FEATURES directory. This isolates specific feature knowledge for agents working on isolated components.

How do agents stay up-to-date with recent repository changes after spawning?

To keep agents up-to-date with recent repository changes after spawning, update a DELTA_CONTEXT.md file by running `cms update`. This captures recent changes to maintain agent knowledge with low overhead.

Can I use portable context artifacts for multi-agent pipelines?

Yes, you can use portable context artifacts for multi-agent pipelines. The system provides stable BOOT_CONTEXT and per-feature bundles that enable token-efficient knowledge transfer and reliable state rehydration across distributed agents.