sprout-docs

Generate per-folder README-style documentation with incremental state tracking.

2|5|Updated Jan 2, 2026
One-click install
npx skills add https://github.com/whoabuddy/claude-knowledge --skill sprout-docs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sprout-docs
Source: https://github.com/whoabuddy/claude-knowledge/tree/main/claude-config/skills/sprout-docs
Command: npx skills add https://github.com/whoabuddy/claude-knowledge --skill sprout-docs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually exploring large codebases and keeping folder-level context up-to-date is time-consuming; sprout-docs automates generation of navigable per-folder README-style documentation that helps you explore structures quickly.

Core Features & Use Cases

  • Generates a gitignored sprout-docs/ folder containing per-folder documentation for quick navigation.
  • Keeps state locally (sprout-docs/.state.json) to enable incremental updates without re-writing unchanged pages.
  • Works across repositories to reveal folder contents and relationships for exploration and onboarding.

Quick Start

Generate local folder docs for your repository by running the documentation generator on the root of your project.

Frequently Asked Questions about sprout-docs

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

FAQPage Schema
How do I generate navigable folder documentation for a large codebase?

Generate navigable folder documentation by running the documentation generator on your project root, which creates a gitignored sprout-docs/ folder containing per-folder README-style pages for quick directory exploration and onboarding.

What is the best way to explore directory structures in a local code repository?

Exploring directory structures locally is best handled by generating per-folder README-style pages that reveal folder contents and relationships, allowing you to navigate complex code repositories quickly without manual inspection.

Can I incrementally update codebase documentation without rewriting unchanged pages?

You can incrementally update codebase documentation without rewriting unchanged pages because the generator stores change state locally in sprout-docs/.state.json, tracking modifications to ensure only updated folders receive new documentation.

Does folder documentation generation work for repositories of any size?

Folder documentation generation works for repositories of any size, applying automated per-folder README creation across small and large projects to facilitate code discovery and streamline the onboarding process.

How do I keep codebase folder context up-to-date automatically?

Keep codebase folder context up-to-date automatically by utilizing the local state tracking file, which enables incremental updates to navigable documentation pages whenever directory structures or contents change.

What is a local README generator and when do I need it for code exploration?

A local README generator automates per-folder documentation creation for code repositories, needed when manually exploring large codebases becomes time-consuming and you require navigable pages for quick code discovery and onboarding.