sync-coord

Synchronize project coordination documentation within a defined .coord/ structure.

Updated Nov 8, 2025

Search Tags:#workflow #project management #documentation #context management #coordination #system steward

Ready to run

npx skills add https://github.com/elevanaltd/eav-cep-assist --skill sync-coord

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: sync-coord
Source: https://github.com/elevanaltd/eav-cep-assist/tree/main/.claude/skills/sync-coord
Command: npx skills add https://github.com/elevanaltd/eav-cep-assist --skill sync-coord

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the management and synchronization of project documentation across different contexts, ensuring consistency and up-to-date information for system stewards and orchestrators.

Core Features & Use Cases

Centralized Documentation Management: Organizes and maintains project coordination documents within a defined .coord/ structure.
Contextual Updates: Provides clear patterns for updating PROJECT-CONTEXT.md and APP-CONTEXT.md based on project phases, decisions, and changes.
Delegation Workflow: Facilitates the delegation of documentation updates from a holistic-orchestrator to a system-steward with defined tasks and handoff packets.
Worktree Pattern: Enables documentation changes to be made in a separate worktree, ensuring a clean main branch.
Use Case: When a new phase of a project is completed, this Skill can be used to update the relevant project context files, ensuring all stakeholders have the latest information on project status, decisions, and next actions.

Quick Start

Use the sync-coord skill to update the project context documentation.

Frequently Asked Questions about sync-coord

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

FAQPage Schema

How do I synchronize project documentation across different contexts?▼

Synchronizing project documentation involves maintaining contextual files like `PROJECT-CONTEXT.md` and `APP-CONTEXT.md` within a `.coord/` structure, ensuring all stakeholders access up-to-date status, decisions, and next actions across different contexts.

What is the best way to update project context files after a phase transition?▼

Updating project context files after a phase transition is handled by enforcing documentation placement rules and naming conventions. This process updates contextual files based on quality gate changes and system infrastructure modifications, ensuring stakeholders have the latest information.

How does the delegation workflow work for documentation updates?▼

The delegation workflow for documentation updates facilitates structured tasks and handoff packets from a `holistic-orchestrator` to a `system-steward`. This ensures system stewards receive defined documentation update instructions without manual orchestration overhead.

Can I use a separate worktree to manage coordination documentation changes?▼

Yes, you can use a worktree pattern to manage coordination documentation changes. This approach enables updates to be made in a separate worktree, ensuring the main branch remains clean while synchronizing project context files.

Does this documentation synchronization approach enforce specific naming conventions for reports?▼

Yes, this documentation synchronization approach enforces strict documentation placement rules and naming conventions for reports. It ensures coordination documents are organized predictably within the `.coord/` structure during infrastructure modifications.