ai-sync-state

Re-reads TASKS.md, architect.md, and DIGEST.md from the filesystem to synchronize cross-agent context.

Updated Feb 26, 2026
One-click install
npx skills add https://github.com/Vimurai/ai-os --skill ai-sync-state-vimurai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ai-sync-state
Source: https://github.com/Vimurai/ai-os/tree/main/.claude/skills/ai-sync-state
Command: npx skills add https://github.com/Vimurai/ai-os --skill ai-sync-state-vimurai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When the Architect and Engineer agents run in separate terminal sessions, one agent's context window becomes stale after the other modifies shared .ai/ memory files, leading to decisions based on outdated task state. ## Core Features & Use Cases - Forced Filesystem Re-Read: Explicitly re-reads .ai/TASKS.md, .ai/architect.md, and .ai/DIGEST.md, bypassing any cached conversational copy. - State Extraction: Pulls open E-##/P-##/T-## tasks, the last completed task, blueprint version markers, and Triad health from the freshly read files. - Structured Sync Report: Outputs a compact [SYNC-STATE] confirmation with open task counts, last completion, blueprint version, and a CLEAN/ACTIVE status. - Use Case: Before the Engineer starts implementing a task, invoke this skill to confirm the Architect's latest TASKS.md changes instead of trusting stale conversation history. ## Quick Start Ask the agent to run the ai-sync-state skill to re-read the current .ai/ memory files and report the latest open tasks before continuing work.

Frequently Asked Questions about ai-sync-state

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

FAQPage Schema
How do I sync context between two AI agents in separate terminals?▼

Invoke the ai-sync-state skill at every handoff. It forces a fresh filesystem read of TASKS.md, architect.md, and DIGEST.md so the receiving agent discards stale conversational memory and works from current state.

How to check open tasks in an AI-OS project before starting work?▼

Run the sync skill, which parses .ai/TASKS.md for all unchecked E-##, P-##, and T-## items and reports them in a compact [SYNC-STATE] block along with the last completed task.

Does ai-sync-state modify any project files?▼

No, the skill is strictly read-only. It only reads TASKS.md, architect.md, and DIGEST.md from the filesystem and reports their state; it never writes to or alters any file.

What happens if a memory file is missing during sync?▼

The skill outputs a [SYNC-STATE] WARNING naming the missing file and instructs you to run ai init to restore the AI-OS memory structure before proceeding.

When should I not rely on conversational memory for task state?▼

Never rely on it after the other agent may have edited .ai/ files. Conversational copies become stale immediately after external modification, so the skill mandates a hard re-read before any planning or implementation decision.