documentation-sync

Update and validate six documentation files for Cursor and Claude Code agents.

1|2|Updated Dec 3, 2025
One-click install
npx skills add https://github.com/jayhjenkins/ProductOSv0.2 --skill documentation-sync-jayhjenkins
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: documentation-sync
Source: https://github.com/jayhjenkins/ProductOSv0.2/tree/main/.claude/skills/quality-gates/documentation-sync
Command: npx skills add https://github.com/jayhjenkins/ProductOSv0.2 --skill documentation-sync-jayhjenkins

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill ensures documentation consistency across Cursor and Claude Code agents by updating and validating six critical documentation files whenever skills, workflows, quality gates, or context assembly patterns are created or modified, preventing divergence and misalignment.

Core Features & Use Cases

  • Enforces the Iron Law: NO SKILL COMPLETE WITHOUT DOCUMENTATION SYNC.
  • Coordinates updates across the six documentation files: .claude/CLAUDE.md, CLAUDE.md, CURSOR-PM-SYSTEM.md, AGENTS.md, README.md, and all .cursor/rules/*.mdc.
  • Validates cross-references and maintains cross-file consistency during skill creation or modification, including the documentation-update matrix and validation procedures.

Quick Start

Follow the documentation-sync process whenever you create or modify a skill. Identify required files with the matrix, update all files with consistent skill naming and descriptions, and run the validation checklist to ensure completeness and cross-reference integrity.

Frequently Asked Questions about documentation-sync

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

FAQPage Schema
How do I keep Claude Code and Cursor documentation consistent when updating skills?

To keep Claude Code and Cursor documentation consistent, you must synchronize updates across six critical files: .claude/CLAUDE.md, CLAUDE.md, CURSOR-PM-SYSTEM.md, AGENTS.md, README.md, and .cursor/rules/*.mdc files whenever skills or workflows are modified.

What is cross-file consistency for quality gates and context assembly patterns?

Cross-file consistency for quality gates ensures that modifications to workflows or context assembly patterns are accurately reflected and validated across all six project documentation files to prevent configuration divergence.

How do I validate documentation updates across multiple agent configuration files?

You validate documentation updates by running a validation checklist that verifies cross-reference integrity and ensures consistent skill naming and descriptions across the six required documentation files.

Does this documentation sync process work with both Cursor and Claude Code agents?

Yes, this documentation sync process works with both Cursor and Claude Code agents by enforcing updates to shared files like CLAUDE.md and AGENTS.md alongside Cursor-specific rules.

When do I need to update project documentation files for skill management?

You need to update project documentation files whenever you create or update new skills and workflows, modify quality gates, or adjust context assembly patterns to maintain cross-file consistency.

Why does documentation diverge when managing skills across multiple AI agent platforms?

Documentation diverges because multiple agent platforms use separate configuration files, requiring a synchronization process to update all six critical files simultaneously and prevent misalignment.