update-docs

Update changelogs, functionality docs, tech docs, and archived plans after feature releases.

Updated Apr 11, 2026
One-click install
npx skills add https://github.com/fullstackray/adulting.diy --skill update-docs-fullstackray
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: update-docs
Source: https://github.com/fullstackray/adulting.diy/tree/main/.claude/skills/update-docs
Command: npx skills add https://github.com/fullstackray/adulting.diy --skill update-docs-fullstackray

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

After feature work, project documentation often lags behind, leading to out-of-date changelogs, product and tech docs, CLAUDE.md, and plan records. This skill ensures documentation stays synchronized with code and decisions, reducing manual overhead and preventing knowledge gaps.

Core Features & Use Cases

  • Updates the changelog under docs/functionality/changelog.md with today's date and concise user-focused entries.
  • Creates or updates Functionality Docs (docs/functionality/) and Tech Docs (docs/tech/) to reflect new behavior and usage, with cross-links to related docs.
  • Updates CLAUDE.md and archives completed plans in docs/plans/completed/ when guided by project workflows.

Quick Start

Trigger update-docs after feature work to refresh changelog, docs, and plan archives.

Frequently Asked Questions about update-docs

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

FAQPage Schema
How do I automatically update project documentation after releasing a new feature?

You can automatically update documentation after a feature release by triggering a workflow that refreshes the changelog, functionality docs, tech docs, and CLAUDE.md with the latest changes.

What is the best way to keep a changelog and technical docs synchronized with code changes?

Keeping docs synchronized involves automating post-feature maintenance to update changelogs and tech docs, preventing manual overhead and ensuring documentation accurately reflects current code behavior.

How do I archive completed project plans and update CLAUDE.md after feature work?

To archive completed plans and update CLAUDE.md, you can trigger an automated documentation workflow that moves plans to a completed folder and refreshes project context.

Do I need existing doc templates to automate functionality and tech docs updates?

Yes, automating functionality and tech docs updates requires existing templates in your docs/functionality/ and docs/tech/ folders, alongside a CLAUDE.md file.

Can I validate cross-links between functionality docs and tech docs automatically?

Yes, automated documentation maintenance validates cross-links between functionality docs and tech docs while preserving historical changes to ensure structural integrity.

What should I do if my documentation workflow does not support a structured docs folder?

If your project lacks a structured docs folder, this automated documentation approach is not suitable; it specifically targets software projects with organized docs/functionality/ and docs/tech/ directories.