builder-living-docs-k

Update living docs and diagrams after each implementation pass.

1|Updated Jan 25, 2026
One-click install
npx skills add https://github.com/JSai23/claude-tooling --skill builder-living-docs-k
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: builder-living-docs-k
Source: https://github.com/JSai23/claude-tooling/tree/main/plugins/wf/skills/builder-living-docs-k
Command: npx skills add https://github.com/JSai23/claude-tooling --skill builder-living-docs-k

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Living documentation tends to become outdated as code evolves, creating misalignment between implementation and references. This skill enforces that documentation remains a core output, with up-to-date living docs, diagrams, and ARCHITECTURE.md aligned to the current system.

Core Features & Use Cases

  • After every implementation pass, update living docs to reflect the new reality.
  • Maintain diagram accuracy using Mermaid for formal diagrams and ASCII for quick overviews.
  • Reconcile living docs with ARCHITECTURE.md to ensure a single source of truth and smooth handoffs between agents.

Quick Start

Update living docs and diagrams to reflect the current system shape after every implementation pass.

Frequently Asked Questions about builder-living-docs-k

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

FAQPage Schema
How do I keep architecture documentation in sync with code changes?

To keep architecture documentation in sync with code changes, you must update living docs after every implementation pass to reflect the new system reality and reconcile references with ARCHITECTURE.md.

What is the best way to maintain living docs using Mermaid and ASCII diagrams?

Maintaining living docs with Mermaid and ASCII diagrams requires refreshing formal structural visualizations and quick overview representations after implementation to ensure they match the current codebase.

How do I reconcile ARCHITECTURE.md with living docs for agent handoffs?

Reconciling ARCHITECTURE.md with living docs establishes a single source of truth for the system, ensuring smooth handoffs between agents and accurate cross-module references.

When do I need to update living documentation during software development workflows?

You need to update living documentation during software development workflows after every implementation pass to prevent misalignment between the evolving code and the existing references.

Does updating living docs require any specific diagram formats?

Updating living docs uses Mermaid for formal diagrams and ASCII for quick overviews, ensuring structural visualizations and fast references remain accurate across modules.