dev.document

Record documentation changes across README.md, DESIGN.md, CLAUDE.md, AGENTS.md, and NEXT_STEPS.md.

6|Updated Nov 10, 2025
One-click install
npx skills add https://github.com/kevinslin/llm --skill dev-document
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dev.document
Source: https://github.com/kevinslin/llm/tree/main/skills/dev.document
Command: npx skills add https://github.com/kevinslin/llm --skill dev-document

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams ensure project documentation stays up to date by automatically noting and recording changes across key files.

Core Features & Use Cases

  • Tracks edits to essential docs (README.md, DESIGN.md, CLAUDE.md, AGENTS.md, NEXT_STEPS.md) to ensure alignment after changes.
  • Validates presence of the specified files and prompts for updates when discrepancies are detected.

Quick Start

Run a doc-update pass to align the designated documentation files with your latest changes.

Frequently Asked Questions about dev.document

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

FAQPage Schema
How do I track changes across project documentation files like README and DESIGN?

To track changes across project documentation, this solution identifies and records edits to core docs such as README.md and DESIGN.md, verifying presence and consistency after each update to keep notes aligned.

What is the best way to keep documentation consistent after code changes?

The best way to keep documentation consistent is running a doc-update pass. This enforces the presence of designated files like NEXT_STEPS.md and AGENTS.md, providing a minimal, repeatable workflow to align notes with latest changes.

Can I enforce the presence of specific markdown docs in my repository?

Yes, you can enforce the presence of specific markdown docs. The skill validates the existence of designated files including README.md, DESIGN.md, CLAUDE.md, AGENTS.md, and NEXT_STEPS.md, prompting for updates when discrepancies are detected.

How do I automate documentation updates for core project files?

You automate documentation updates by running a doc-update pass. This action scans core project files, records any detected changes, and prompts for necessary updates to maintain alignment across all tracked documentation.

What files are included in documentation change tracking?

Files included in documentation change tracking are README.md, DESIGN.md, CLAUDE.md, AGENTS.md, and NEXT_STEPS.md. These designated files are checked for presence and consistency after each recorded change.