excavate

Generate one feature spec per excavation for codebases with identifiable entry points.

6|Updated Oct 7, 2025

Search Tags:#documentation #codebase #spec #feature #mapping #excavate

Ready to run

npx skills add https://github.com/rjroy/vibe-garden --skill excavate

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: excavate
Source: https://github.com/rjroy/vibe-garden/tree/main/lore-development/skills/excavate
Command: npx skills add https://github.com/rjroy/vibe-garden --skill excavate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams document an existing codebase by producing one feature-spec document per excavation, enabling a manageable map of system capabilities over time.

Core Features & Use Cases

Progressive discovery: Document one feature at a time to build a navigable feature map.
Entry-point tracing: Identify API routes, CLI commands, UI components, and message handlers to map how users interact with the code.
Reference generation: Create per-feature .lore/reference documents and maintain an excavation index for traceability.

Quick Start

/lore-development:excavate

Frequently Asked Questions about excavate

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

FAQPage Schema

How do I document codebase features progressively without getting overwhelmed?▼

Progressive codebase documentation generates one feature spec per excavation, creating a manageable map of system capabilities over time instead of documenting everything at once.

What is the best way to map API routes and CLI commands to user-facing features?▼

Mapping API routes and CLI commands involves tracing identifiable entry points to generate per-feature reference documents, linking them in an excavation index for system navigation.

Can I trace UI components and message handlers to build a feature map for an existing codebase?▼

Yes, tracing UI components and message handlers identifies how users interact with the code, enabling a progressive feature map through per-feature spec generation and reference documentation.

How does generating one feature spec at a time help document an existing codebase?▼

Generating one feature spec per excavation breaks codebase documentation into manageable steps, producing navigable `.lore/reference` documents and maintaining an excavation index for traceability.

Does this approach work for codebases with identifiable entry points like API routes?▼

Yes, progressive excavation applies to codebases with identifiable entry points such as API routes, CLI commands, and UI components, generating per-feature reference documents under `.lore/reference`.

What are the limitations of progressive codebase excavation for feature documentation?▼

Progressive excavation requires codebases with identifiable entry points like API routes or UI components; codebases without clear entry points cannot be progressively mapped using this feature spec approach.