context-snapshot

Captures frozen project state snapshots before parallel subagent dispatch and stage transitions.

Updated Jun 12, 2026
One-click install
npx skills add https://github.com/oleyna80/agentic-sdlc-framework --skill context-snapshot-oleyna80
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: context-snapshot
Source: https://github.com/oleyna80/agentic-sdlc-framework/tree/main/skills/context-snapshot
Command: npx skills add https://github.com/oleyna80/agentic-sdlc-framework --skill context-snapshot-oleyna80

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When multiple subagents run in parallel or a session resumes after interruption, agents can operate on desynchronized views of the project, leading to contradictory decisions. This Skill freezes the current system state — memory bank, file state, agent topology, constraints, and recovery plan — into a single read-only snapshot so every subagent starts from the same baseline. ## Core Features & Use Cases - State Freezing: Captures memory bank files (context.md, progress.md, decisions.md, orchestrator-log.md), git status, and recently added files into a timestamped snapshot under memory_bank/snapshots/. - Isolation Zone Mapping: Defines which files each parallel agent owns versus shares, plus constraints on files not to touch and decisions not to reconsider. - Recovery Planning: Records per-agent timeout handling, conflict resolution, and stale-snapshot actions for session resume scenarios. - Use Case: Before dispatching three parallel review subagents on Work Block wb-003, create a snapshot so each agent's mission brief references the same frozen state, and archive it afterward as part of the audit trail. ## Quick Start Ask the Control Tower to create a context snapshot for work block wb-003 at stage 0 before dispatching the parallel subagents.

Frequently Asked Questions about context-snapshot

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

FAQPage Schema
How do I keep parallel subagents synchronized on the same project state?▼

Create a context snapshot before dispatching parallel subagents. The snapshot freezes the memory bank, git status, agent topology, and constraints into one file that every subagent reads, preventing contradictory decisions from desynchronized context.

When should I create a context snapshot in a multi-agent workflow?▼

Create one when spawning two or more parallel subagents, launching a Workflow tool run, transitioning stages with pending subagent tasks, or resuming a session after interruption. Skip it for single subagents, sequential execution, or trivial work blocks.

Can subagents modify or create context snapshots?▼

No. Snapshots are read-only for subagents and immutable after creation. Only the Control Tower creates and archives them, and subagents report suspected staleness back to the Control Tower instead of editing the file.

What information does a context snapshot contain?▼

A snapshot records the current work block, stage, write gate status, memory bank summaries, git status and recent files, per-agent isolation zones, constraints such as files not to touch, and a recovery plan covering hangs, conflicts, and staleness.

What are the limitations of context snapshots?▼

Snapshots add no value for single-subagent or sequential work and must never contain secrets like .env values or tokens. They also cannot be edited after dispatch, so a stale snapshot requires Control Tower intervention rather than an in-place fix.