project-state-sync

Ingest raw project material into structured work orders and decision logs.

4|Updated Dec 7, 2025
One-click install
npx skills add https://github.com/grigb/gas-prompt-library --skill project-state-sync
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: project-state-sync
Source: https://github.com/grigb/gas-prompt-library/tree/main/agents/agent-project-state-sync
Command: npx skills add https://github.com/grigb/gas-prompt-library --skill project-state-sync

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill solves the fragmentation of project information by automating the aggregation, translation, and reconciliation of project state across disparate sources like transcripts, conversations, and inbox packets.

Core Features & Use Cases

  • Deterministic Ingestion: Automatically tracks and ingests new project material since the last sync without duplicating data.
  • Structured Reconciliation: Reuses established stewardship machinery to update work orders, decision logs, and project status surfaces.
  • Use Case: A project manager can use this to catch up on all project activity since their last review, ensuring that meeting outcomes, new decisions, and pending tasks are correctly reflected in the project's documentation without manual entry.

Quick Start

Invoke the project state sync skill to aggregate all new project material and reconcile the current state since the last run.

Frequently Asked Questions about project-state-sync

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

FAQPage Schema
How do I automate reconciliation of meeting transcripts and inbox packets into project documentation?

Project state reconciliation automates the aggregation and translation of disparate sources like meeting transcripts and inbox packets into structured work orders and decision logs. It uses deterministic ingestion scripts to ensure idempotent state updates without duplicating data.

What is the best way to sync project state from conversation logs without manual entry?

Syncing project state from conversation logs is handled by ingesting raw source material since the last run and translating it into structured work orders. Established stewardship machinery reuses deterministic scripts to update project status surfaces without manual data entry.

Does project state sync support multi-project scopes or is it limited to single projects?

Project state sync operates on single-project scopes to maintain consistency across meeting transcripts, conversation logs, and inbox packets. It requires deterministic ingestion scripts and established reconciliation machinery to ensure idempotent state updates within that boundary.

How do I prevent duplicate data when aggregating new project material since the last sync?

To prevent duplicate data during aggregation, deterministic ingestion automatically tracks and ingests new project material since the last sync. This idempotent approach ensures raw source material is translated into structured work orders without duplicating existing entries.

Why do I need established reconciliation machinery to update work orders and decision logs?

Reconciliation machinery is required to reuse established stewardship workflows and ensure idempotent state updates. Without it, the deterministic ingestion scripts cannot reliably translate raw source material into structured work orders and decision logs.

Can I use PyYAML to configure deterministic ingestion scripts for project state synchronization?

PyYAML is required as a dependency to configure and run the deterministic ingestion scripts used for project state synchronization. It supports the translation of raw source material into structured work orders and decision logs within single-project scopes.