gsd-update

Update planning documents from Git history and diffs.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/optivent/gsd-kimi-cli --skill gsd-update
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-update
Source: https://github.com/optivent/gsd-kimi-cli/tree/main/skills/gsd-update
Command: npx skills add https://github.com/optivent/gsd-kimi-cli --skill gsd-update

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Update planning documents to reflect code changes, preventing drift between implementation and documentation.

Core Features & Use Cases

  • Automatically scan recent commits and diffs to find changes impacting REQUIREMENTS.md, ROADMAP.md, STATE.md.
  • Update planning artifacts to reflect code changes, and flag discrepancies for review.
  • Use cases include onboarding, Brownfield projects, and mid-project course corrections.

Quick Start

Run the gsd-update command to synchronize your planning docs with the latest code changes.

Frequently Asked Questions about gsd-update

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

FAQPage Schema
How do I synchronize planning documents with recent Git changes?

To synchronize planning documents with recent Git changes, you can run the gsd-update command to automatically scan commit history and diffs, updating REQUIREMENTS.md, ROADMAP.md, and STATE.md to reflect code evolution. This ensures your planning artifacts remain consistent and auditable.

What is planning document drift and how do I fix it?

Planning document drift occurs when your implementation evolves but your documentation does not. You fix code drift by analyzing Git history and diffs to identify discrepancies, then automatically updating planning artifacts to accurately reflect the current state of the codebase.

Can I update REQUIREMENTS.md and ROADMAP.md automatically from Git commits?

Yes, you can update REQUIREMENTS.md and ROADMAP.md automatically from Git commits. The tool scans recent commits and diffs to find changes impacting these specific planning files, flags discrepancies for review, and ensures updates are consistent and ready for review.

Does this work for onboarding and brownfield project documentation?

Yes, this works for onboarding and brownfield project documentation. Synchronizing planning docs with code changes is particularly useful for onboarding new team members, updating legacy brownfield projects, and executing mid-project course corrections.

What's the best way to keep STATE.md updated during mid-project course corrections?

The best way to keep STATE.md updated during mid-project course corrections is to scan recent Git diffs and automatically apply the code changes to your planning artifacts. This flags discrepancies for review and ensures your state tracking remains consistent and auditable.