agent-init-deep

Name: agent-init-deep
Availability: InStock
Author: Ravn

Initialize or migrate projects to a progressive CLAUDE.md structure with docs/agents/.

16|15|Updated Jan 16, 2026

Search Tags:#documentation #project structure #progressive disclosure #CLAUDE.md #docs/agents #root CLAUDE.md

Ready to run

npx skills add https://github.com/ravnhq/ai-toolkit --skill agent-init-deep

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: agent-init-deep
Source: https://github.com/ravnhq/ai-toolkit/tree/main/skills/agent-init-deep
Command: npx skills add https://github.com/ravnhq/ai-toolkit --skill agent-init-deep

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams initialize or migrate to a nested CLAUDE.md structure, enabling progressive disclosure and on-demand topic guidance across a project.

Core Features & Use Cases

Root-structure guidance that splits CLAUDE.md into a concise root file and topic-specific docs under docs/agents/.
Migration assistance for refactoring bloated CLAUDE.md and upgrading projects to progressive disclosure.
Onboarding support for new projects and cross-team handoffs with consistent guidance routing.

Quick Start

Set up a progressive CLAUDE.md layout with a root CLAUDE.md and a docs/agents/ directory. Then explore related agent-guides via the available skills.

Frequently Asked Questions about agent-init-deep

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

FAQPage Schema

How do I migrate a bloated CLAUDE.md to a progressive disclosure structure?▼

To migrate a bloated CLAUDE.md to progressive disclosure, split it into a concise root CLAUDE.md and route topic-specific guidance into files under a docs/agents/ directory, generating contextual files as needed.

What is progressive disclosure for project documentation and how does it work?▼

Progressive disclosure is a project documentation strategy that uses a root CLAUDE.md to load on-demand, topic-specific guidance from a docs/agents/ directory, reducing context bloat by serving contextual files only when needed.

Can I set up a progressive CLAUDE.md layout for a greenfield project?▼

Yes, you can initialize a progressive CLAUDE.md layout for greenfield projects by scaffolding a root CLAUDE.md and a docs/agents/ directory, creating topic-specific files incrementally as the project grows.

What's the best way to organize CLAUDE.md files for cross-team handoffs?▼

The best way to organize CLAUDE.md files for cross-team handoffs is a nested structure with a root CLAUDE.md and topic-specific docs under docs/agents/, ensuring consistent guidance routing and onboarding support.

When should I not use a nested CLAUDE.md structure?▼

You should avoid a nested CLAUDE.md structure if your project documentation is minimal and does not benefit from contextual routing, as the overhead of maintaining a root file and docs/agents/ directory outweighs the progressive disclosure benefits.