seed-docs

Populate documentation stubs with content from CLAUDE.md and codebase analysis.

9|1|Updated Feb 28, 2026
One-click install
npx skills add https://github.com/Roxabi/roxabi-plugins --skill seed-docs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: seed-docs
Source: https://github.com/Roxabi/roxabi-plugins/tree/main/plugins/dev-core/skills/seed-docs
Command: npx skills add https://github.com/Roxabi/roxabi-plugins --skill seed-docs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the population of documentation stubs with real project information, ensuring that architecture, standards, and guides are up-to-date and actionable.

Core Features & Use Cases

  • Automated Stub Filling: Identifies and fills documentation files containing TODO markers or insufficient content.
  • Knowledge Extraction: Gathers relevant information from CLAUDE.md and codebase analysis (structure, naming conventions, stack, etc.).
  • Use Case: After a refactor, run this Skill to automatically update your architecture diagrams and coding standards documentation based on the current state of your codebase and your CLAUDE.md file.

Quick Start

Run the seed-docs skill to populate documentation stubs using CLAUDE.md and codebase analysis.

Frequently Asked Questions about seed-docs

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

FAQPage Schema
How do I automate filling documentation stubs after a codebase refactor?

Automate documentation stub filling by running the skill to extract architecture and coding standards from CLAUDE.md and codebase analysis, automatically populating files containing TODO markers or less than 30 lines with actionable project information.

What is the best way to keep architecture docs updated with current codebase standards?

Keeping architecture docs updated involves extracting knowledge from CLAUDE.md and analyzing codebase structure and naming conventions to populate scaffolded documentation with real, actionable guidance reflecting the current project state.

Does seed-docs work with custom documentation paths and formats?

Yes, it integrates configuration from the .claude/stack.yml file to handle dynamic documentation paths and formats, ensuring extracted codebase knowledge populates the correct scaffolded stub files.

How does the tool identify which documentation files need to be populated?

It identifies documentation stubs by scanning for files containing TODO markers or files with less than 30 lines of content, then fills them with real information extracted from CLAUDE.md and codebase analysis.

Can I use codebase analysis to generate actionable developer guides automatically?

Yes, codebase analysis extracts the project stack, structure, and naming conventions, combining this with CLAUDE.md data to generate actionable guidance for agents and developers within scaffolded documentation files.

What are the limitations of using CLAUDE.md for automated documentation generation?

Automated documentation generation relies on the accuracy of CLAUDE.md and codebase structure, meaning it requires existing scaffolded stub files with TODO markers or under 30 lines to identify and populate targets successfully.