PRD Sync

Align PRD-*.md files in docs/features with detected code changes.

2|Updated May 1, 2026
One-click install
npx skills add https://github.com/nikkogibler/MarsFounderIO --skill prd-sync-nikkogibler
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: PRD Sync
Source: https://github.com/nikkogibler/MarsFounderIO/tree/main/my-instructions/skills/prd-sync
Command: npx skills add https://github.com/nikkogibler/MarsFounderIO --skill prd-sync-nikkogibler

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Documentation drift between code and PRD documents leads to confusion, missed requirements, and degraded product quality. PRD Sync provides a deterministic workflow to detect changes and refresh PRD files so docs stay accurate over time.

Core Features & Use Cases

  • Detects code changes within the workspace in the last 24 hours and identifies the impacted PRD documents.
  • Locates the governing prd-*.md in docs/features/ and updates Core Logic and Data Reality sections to reflect current implementation.
  • Appends a changelog entry to the PRD to capture when and what was updated, ensuring traceability across releases.
  • Supports safe, non-destructive updates by preserving existing structure and only correcting drift where necessary.

Quick Start

Run PRD Sync after code changes to automatically refresh the related PRD files and record the update in the PRD changelog.

Frequently Asked Questions about PRD Sync

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

FAQPage Schema
How do I keep PRD documents in sync with code changes?

To keep PRD documents in sync with code changes, PRD Sync detects workspace modifications from the last 24 hours and automatically updates the matching prd-*.md files. It refreshes Core Logic and Data Reality sections to accurately reflect the current implementation.

What is documentation drift and how do I fix it in feature docs?

Documentation drift occurs when PRD files become outdated as code evolves. You fix it by running PRD Sync, which locates impacted prd-*.md files in docs/features and applies non-destructive edits to correct the outdated content.

How do I update a PRD changelog after modifying feature code?

To update a PRD changelog after modifying feature code, PRD Sync automatically appends a traceable entry to the governing PRD document. This records when and what was updated during the synchronization process.

Can I automatically update PRD files without losing existing formatting?

Yes, you can update PRD files without losing existing formatting because PRD Sync applies safe, non-destructive edits. It preserves the existing document structure and only corrects drift where necessary within the Core Logic and Data Reality sections.

What is the best way to maintain quality assurance for PRD versioning?

The best way to maintain quality assurance for PRD versioning is to run PRD Sync after code changes. It deterministically aligns documentation with the latest implementation and maintains traceability by appending a changelog entry to the PRD.