playbooks

home / skills / kevinslin / llm / dev.document

dev.document skill

/skills/dev.document

This skill updates project documentation to reflect changes, ensuring README.md, DESIGN.md, CLAUDE.md, AGENTS.md, and NEXT_STEPS.md are current.

npx playbooks add skill kevinslin/llm --skill dev.document

Review the files below or copy the command above to add this skill to your agents.

Files (1)
SKILL.md
270 B
---
name: dev.document
description: document changes made
version: 0.0.0
---

Update all relevant documentation based on the changse you made. 

Make sure to always check the following files if they exist:
- README.md
- DESIGN.md
- CLAUDE.md
- AGENTS.md
- NEXT_STEPS.md

Overview

This skill documents changes made to a codebase by updating all relevant documentation files. It ensures documentation stays synchronized with code and captures rationale, usage, and migration notes. The result is clearer context for reviewers and future maintainers.

How this skill works

The skill scans the project for common documentation files (README.md, DESIGN.md, CLAUDE.md, AGENTS.md, NEXT_STEPS.md) and updates them with summaries of the changes you performed. It generates concise change notes, updates usage examples or API snippets if required, and inserts migration or rollout instructions. It also flags missing documentation files and suggests targeted edits to keep docs complete and consistent.

When to use it

  • After implementing feature changes or bug fixes
  • When refactoring code or changing public APIs
  • Prior to opening a pull request or requesting a review
  • When preparing a release or publishing packages
  • When onboarding new contributors or updating design decisions

Best practices

  • Write concise, action-oriented change summaries that explain why, not just what
  • Update README.md with new installation, usage, and API highlights when interfaces change
  • Record design trade-offs and alternatives in DESIGN.md for future reference
  • Keep CLAUDE.md and AGENTS.md aligned with agent behavior and configuration changes
  • Use NEXT_STEPS.md to capture follow-up tasks, migration steps, and rollout considerations

Example use cases

  • You renamed a public function: update README examples, note migration steps, and add a short rationale in DESIGN.md.
  • You refactored internal architecture: document the new approach in DESIGN.md and list follow-up tasks in NEXT_STEPS.md.
  • You added an automated agent or bot: update AGENTS.md with configuration, capabilities, and safety notes.
  • You changed contributor or legal process: add or edit CLAUDE.md to reflect updated CLA or contribution steps.
  • You prepared a release: consolidate user-facing changes in README.md and list post-release monitoring actions in NEXT_STEPS.md.

FAQ

Which files does the skill check and update?

It targets README.md, DESIGN.md, CLAUDE.md, AGENTS.md, and NEXT_STEPS.md if they exist, and will suggest edits when files are missing.

How detailed should the change notes be?

Keep notes concise but informative: include what changed, why, API implications, and any migration or rollback steps.