active-context

Read and update specs/.session-context.md to track decisions and blockers.

Updated Apr 19, 2026
One-click install
npx skills add https://github.com/PytaichukBohdan/AndriiPresentation --skill active-context
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: active-context
Source: https://github.com/PytaichukBohdan/AndriiPresentation/tree/main/.claude/skills/active-context
Command: npx skills add https://github.com/PytaichukBohdan/AndriiPresentation --skill active-context

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Read and respect the shared session context before starting any task to prevent duplicated work and misaligned efforts.

Core Features & Use Cases

  • Reads specs/.session-context.md at the start of a task to understand what has been decided, what is in progress, what has been completed, and any blockers.
  • Updates the context file when your work changes the shared state, ensuring future agents have up-to-date guidance.
  • Helps teams and agents coordinate across multiple tasks to avoid conflicts and promote progressive collaboration.

Quick Start

Read the current session context from specs/.session-context.md and incorporate its decisions into your plan before proceeding.

Frequently Asked Questions about active-context

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

FAQPage Schema
How do I track shared session context to avoid duplicated work in multi-agent workflows?

Track shared session context by reading and respecting specs/.session-context.md at task start to understand decisions, progress, and blockers, then update it when changes occur to ensure future agents have up-to-date guidance.

What is multi-agent context coordination and how does it prevent conflicting decisions?

Multi-agent context coordination reads a shared session context file before acting to surface conflicts with prior decisions, ensuring agents align efforts and avoid duplicating work across concurrent tasks.

How do I set up decision-tracking for multi-agent cooperation using a session context file?

Set up decision-tracking by creating specs/.session-context.md to log decisions, progress, and blockers. Agents read this file before starting tasks and update it when work changes the shared state.

Can I use a shared session context file to manage blockers across multiple agents?

Yes, you can manage blockers by having agents read the shared session context file at task start to identify existing blockers, then update the file when their work introduces or resolves new blockers.

What's the best way to coordinate multiple agents working on the same project without overwriting progress?

The best way to coordinate multiple agents is reading the shared session context file before acting to understand completed work and prior decisions, then updating it when changes occur to surface conflicts and prevent duplicated efforts.

When should I not use a shared session context file for agent coordination?

You should not use a shared session context file for agent coordination in single-agent workflows where decision-tracking and blocker management are unnecessary, as the overhead of reading and updating specs/.session-context.md provides no collaborative benefit.