Generate one feature spec per excavation for codebases with identifiable entry points.
npx skills add https://github.com/rjroy/vibe-garden --skill excavate
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
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.
.lore/reference documents and maintain an excavation index for traceability./lore-development:excavate
High-intent search queries and answers about installing and using this skill.
Progressive codebase documentation generates one feature spec per excavation, creating a manageable map of system capabilities over time instead of documenting everything at once.
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.
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.
Generating one feature spec per excavation breaks codebase documentation into manageable steps, producing navigable `.lore/reference` documents and maintaining an excavation index for traceability.
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`.
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.
skaile-aiMap codebase structure, entry points, and data flow with file references.
TheWinciGenerate a structured Markdown wiki with architecture maps and Mermaid diagrams from a codebase.
kslhunterTrace code execution paths from entry points to data storage.
i-standard1Reverse-engineer implemented code into formal requirements definitions mapped in spec-map.yml.