update-docs

Automate documentation updates for completed features, patterns, and decisions.

Updated Jan 8, 2026
One-click install
npx skills add https://github.com/wilsonmsalberto/setup-dotfiles --skill update-docs-wilsonmsalberto
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: update-docs
Source: https://github.com/wilsonmsalberto/setup-dotfiles/tree/main/config/claude-code/global/skills/update-docs
Command: npx skills add https://github.com/wilsonmsalberto/setup-dotfiles --skill update-docs-wilsonmsalberto

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams keep project documentation in sync with completed work, ensuring decisions, patterns, and contextual knowledge are properly recorded in the central docs.

Core Features & Use Cases

  • Audit and clean up documentation across .claude/context/, .claude/patterns/, and .claude/plans/
  • Document learnings and decisions from implementation and review cycles
  • Link and consolidate context, patterns, and plans to support future work

Quick Start

Update project documentation after completing features, establishing patterns, or making decisions.

Frequently Asked Questions about update-docs

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

FAQPage Schema
How do I keep project documentation aligned with completed feature work?

To keep documentation aligned with completed feature work, you audit and update central docs to reflect implementation decisions. This skill automates recording architectural decisions and feature completions across project context, patterns, and plans directories.

What is the best way to document established patterns and architectural decisions?

The best way to document established patterns and architectural decisions is by logging them in dedicated directories. This skill automates pattern creation and decision logging cycles, producing structured notes and references for future development.

How do I clean up plans and context docs after a feature implementation cycle?

To clean up plans and context docs after a feature cycle, you audit and consolidate outdated references. This skill automates updates across .claude/context, .claude/patterns, and .claude/plans to satisfy documentation requirements and remove obsolete information.

Can I use this to produce structured notes for context updates and new patterns?

Yes, you can produce structured notes for context updates and new patterns. It audits documentation across the CLAUDE project directories, linking and consolidating context, patterns, and plans to support future work cycles.

Does this documentation update tool work without external dependencies?

Yes, this documentation update tool works without external dependencies. It operates directly on the project's internal structure, auditing and cleaning up files located within the .claude/context, .claude/patterns, and .claude/plans directories.