documentation-manager

Update project documentation to reflect code changes and evolving architecture.

105|16|Updated Jan 18, 2026
One-click install
npx skills add https://github.com/jordanhubbard/loom --skill documentation-manager
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: documentation-manager
Source: https://github.com/jordanhubbard/loom/tree/main/personas/default/documentation-manager
Command: npx skills add https://github.com/jordanhubbard/loom --skill documentation-manager

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keeps project documentation accurate and up-to-date as software changes.

Core Features & Use Cases

  • Documentation governance that ensures code changes are reflected in guides, references, and diagrams.
  • Onboarding and reference materials to help new contributors find what they need quickly.
  • Architecture and API documentation alignment to reflect evolving systems.
  • Use Case: When a PRD updates or a feature ships, update user guides and API references to maintain consistency.

Quick Start

Review code changes and update relevant docs to reflect the latest features and architecture.

Frequently Asked Questions about documentation-manager

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

FAQPage Schema
How do I keep project documentation accurate and up-to-date as software changes?

To keep project documentation accurate and up-to-date as software changes, review code changes and update relevant user guides, API references, and architecture diagrams to reflect the latest features.

What is the best way to maintain API documentation alignment for evolving systems?

API documentation alignment for evolving systems involves reviewing software changes and updating references to ensure the documentation reflects the latest architecture and features.

How do I update user guides and API references when a feature ships?

When a feature ships or a PRD updates, update user guides and API references by reviewing the code changes and applying them to maintain consistency across all onboarding materials.

Does this approach support onboarding new developers with living documentation?

Yes, this approach supports onboarding new developers by maintaining living documentation, ensuring architecture docs and reference materials are updated through hands-on verification of code changes.

What is the process for changelog maintenance in software projects?

Changelog maintenance in software projects involves reviewing code changes and updating the changelog alongside user guides and architecture docs to ensure all documentation remains consistent.

When do I need living documentation for technical writing?

You need living documentation for technical writing when software changes frequently, requiring continuous updates to user guides, API references, and architecture docs to maintain accuracy.