pmstudio-synclisted

Use when a project has linked documentation artifacts (PRDs, presentations, meeting notes, architecture maps) that must stay synchronized. Detects which source files changed, identifies downstream documents needing updates, reads new content, and proposes specific edits with diffs before applying. Also use when a .sync-report.md exists in the project or user says "process sync report".
rkz91/coco · ★ 3 · AI & Automation · score 69

Install: claude install-skill rkz91/coco

# Doc Sync — Cascading Document Updater ## What This Skill Does Maintains consistency across a documentation ecosystem where one source change (e.g., a new meeting note) should cascade updates to multiple downstream documents (PRD, presentation, project memory). **This is NOT a background watcher.** This skill is the Claude-side processor that: 1. Reads a sync report or detects changes directly 2. Extracts actionable content from new/modified source files 3. Proposes specific edits to each downstream target 4. Applies changes only after user approval ## Prerequisites ### Infrastructure (one-time setup) The persistent detection layer runs outside Claude Code via `/project-sync init`: | Component | Path | Purpose | |-----------|------|---------| | Orchestrator | `~/.claude/scripts/project-sync-orchestrator.sh` | Email search + file detection + report generation | | launchd agent | `~/Library/LaunchAgents/com.claude.project-sync.<name>.plist` | Background scheduler (every 2 hours) | | State dir | `~/.claude/state/<project-name>/` | Logs, timestamps, cached config (outside OneDrive) | ### Per-Project Config Each project needs `.sync-watch.json` in its root: ```json { "project_name": "My Project", "watch_dirs": ["docs/meeting-notes", "docs/research"], "target_docs": { "tier1": [ { "path": "docs/PRD.html", "name": "Product Requirements", "update_from": ["meeting-notes", "research"], "what": "Requirements, user stories, decis