context-circulation

Name: context-circulation
Availability: InStock
Author: tasai-lab

Coordinate subagent context using structured commit messages as the source of truth.

Updated Aug 23, 2026

Search Tags:#workflow #collaboration #context #commit #subagents #context-sharing

Ready to run

npx skills add https://github.com/tasai-lab/fractal-dev-workflow --skill context-circulation

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: context-circulation
Source: https://github.com/tasai-lab/fractal-dev-workflow/tree/main/skills/context-circulation
Command: npx skills add https://github.com/tasai-lab/fractal-dev-workflow --skill context-circulation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Communicate and preserve contextual knowledge across multiple subagents by treating commits as the source of truth.

Core Features & Use Cases

Commit-driven context propagation: Each subagent contributes and reads context from a structured commit history to maintain continuity.
Session resilience: Allows workflows to recover by inspecting recent commits when a session is interrupted.
Auditable collaboration: Provides an auditable trail of decisions and context for downstream reviews.

Quick Start

Begin a new session by committing progress with clear messages, then have the next subagent read the log to understand context.

Frequently Asked Questions about context-circulation

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

FAQPage Schema

How do I share context between subagents in a long-running workflow?▼

To share context between subagents, use commit messages as the source of truth. This context-sharing pattern preserves knowledge across multiple agents and sessions by storing contextual updates in a structured commit history.

What is the best way to recover a multi-agent workflow session after an interruption?▼

The best way to recover an interrupted multi-agent workflow is by inspecting recent commits. This session resilience mechanism allows the next subagent to read the commit log and understand the exact context of previous decisions.

How do subagents maintain context continuity across different sessions?▼

Subagents maintain context continuity by reading and writing to a shared commit history. Each subagent contributes structured commit messages, ensuring that downstream agents can recover and apply the contextual knowledge from previous sessions.

Can I use commit messages to coordinate multiple subagents in a software engineering task?▼

Yes, you can coordinate multiple subagents by enforcing a commit-based context-sharing pattern. Each subagent commits its progress with clear messages, creating an auditable trail of decisions that downstream agents can review.

Why does context get lost when switching between subagents in a multi-agent workflow?▼

Context gets lost when subagents do not persist their progress in a shared source of truth. Committing context to a structured commit history prevents this loss by propagating decisions across agents and enabling session recovery.

Does this context-sharing approach work for long-running workflows with multiple subagents?▼

Yes, this approach is specifically designed for long-running, multi-subagent workflows where context must persist. By treating commits as the source of truth, it enforces continuity and provides an auditable trail for downstream reviews.