design-groom

Validate and synchronize design documentation against current source code.

Updated Mar 24, 2026
One-click install
npx skills add https://github.com/spencerbeggs/design-docs-plugin --skill design-groom
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-groom
Source: https://github.com/spencerbeggs/design-docs-plugin/tree/main/plugin/skills/design-groom
Command: npx skills add https://github.com/spencerbeggs/design-docs-plugin --skill design-groom

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the problem of documentation rot by automating the validation, synchronization, and cleanup of design docs, ensuring they remain accurate reflections of the codebase without manual intervention.

Core Features & Use Cases

  • Autonomous Overhaul: Validates frontmatter, restyles content, and prunes stale context across all project modules.
  • Intelligent Refactoring: Automatically splits oversized documentation into atomic, cross-referenced files and updates all internal CLAUDE.md pointers.
  • Use Case: Before a major release, run this skill to ensure all design documentation is perfectly synced with the current implementation, cross-references are valid, and the project context is clean for new contributors.

Quick Start

Invoke the design-groom skill to perform a full, unattended documentation overhaul across all modules in the project.

Frequently Asked Questions about design-groom

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

FAQPage Schema
How do I automate design documentation synchronization with my source code?

Design documentation synchronization is automated by validating project modules against the current source code, pruning stale context, and reconciling cross-references to ensure docs accurately reflect the codebase.

What is the best way to refactor oversized design docs into smaller files?

Refactoring oversized design docs is handled by automatically splitting them into atomic, cross-referenced files while updating internal CLAUDE.md pointers to maintain structural integrity across the project.

How do I prevent documentation rot before a major software release?

Preventing documentation rot before a release requires running an autonomous validation process across all modules to sync design docs, validate cross-references, and clean project context for new contributors.

Do I need design-doc-agent and context-doc-agent to automate documentation cleanup?

Yes, integration with design-doc-agent and context-doc-agent is required to perform structural updates, validate frontmatter, and commit documentation changes to the repository.

Can git documentation maintenance run unattended across multiple project modules?

Git documentation maintenance can run unattended across all project modules by performing comprehensive validation, restyling content, splitting oversized files, and committing changes directly to the repository.