pmstudio-sync

Cascade documentation updates across PRDs, decks, and knowledge bases with diff-based proposals.

264|11|Updated Apr 25, 2026
One-click install
npx skills add https://github.com/rkz91/coco --skill pmstudio-sync
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pmstudio-sync
Source: https://github.com/rkz91/coco/tree/main/skills/doc-sync
Command: npx skills add https://github.com/rkz91/coco --skill pmstudio-sync

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Maintains consistency across a documentation ecosystem by cascading changes from source content to downstream documents (PRDs, presentations, knowledge bases), reducing manual drift and duplication.

Core Features & Use Cases

  • Detect changes via a sync report or on‑demand, then extract actionable content from updated sources.
  • Propose precise edits to each downstream document with exact diffs, requiring user approval before applying changes.
  • Apply changes across tiered targets (e.g., PRD/html and decks) while preserving formatting and version history.
  • Supports per-project configs to tailor watched directories and target documents.

Quick Start

Start a sync session by running /doc-sync or by saying "process sync report" to review pending updates.

Frequently Asked Questions about pmstudio-sync

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

FAQPage Schema
How do I sync document updates across PRDs, decks, and knowledge bases?

Document sync detects changes via a sync report or on-demand, extracts the updated content, and proposes exact diffs for each downstream document, requiring your explicit approval before applying any edits.

How does diff-based proposal review work for documentation changes?

Diff-based proposal review extracts actionable content from updated sources and presents precise edits for each target document, ensuring you can approve exact changes before they are applied to your knowledge base or PRD.

Can I preserve formatting and version history when syncing content across documents?

Yes, you can preserve formatting and version history when syncing content. The Skill applies approved changes across tiered targets while maintaining the original document structure and historical version logs.

How do I start a sync session to review pending documentation updates?

You start a sync session by running the /doc-sync command or by saying "process sync report" to review pending updates and evaluate the proposed diffs before finalizing the cascade.

Does sync automation require a sync report or can it detect changes on-demand?

Sync automation supports both workflows. It can detect changes on-demand or process a provided sync report to extract actionable content and generate diff-based proposals for your downstream documents.

Can I configure watched directories and target documents for project management documentation?

Yes, you can configure watched directories and target documents for project management documentation. The Skill supports per-project configs to tailor which source files and downstream targets are monitored.