explore-and-document

Explore unfamiliar codebases and document architecture findings.

Updated Nov 2, 2025
One-click install
npx skills add https://github.com/anortham/mcp-toolbox-workflows --skill explore-and-document
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: explore-and-document
Source: https://github.com/anortham/mcp-toolbox-workflows/tree/main/skills/explore-and-document
Command: npx skills add https://github.com/anortham/mcp-toolbox-workflows --skill explore-and-document

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you systematically explore unfamiliar codebases and preserve findings for future reference, combining semantic search, architecture mapping, and persistent documentation.

Core Features & Use Cases

  • Semantic exploration: Quick access to architecture and components.
  • Pattern investigation: Trace call paths and usage patterns.
  • Documentation persistence: Create and store architecture plans and discoveries.

Quick Start

Tell me to "understand this authentication system" and I’ll map the landscape, investigate key patterns, and document the architecture.

Frequently Asked Questions about explore-and-document

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

FAQPage Schema
How do I explore and document an unfamiliar codebase efficiently?

Explore and document codebases by using semantic search to locate architecture components, extracting symbols to map structure, tracing call paths to understand patterns, and creating persistent documentation of your findings. This approach systematizes onboarding and investigation work.

Can I trace call paths and usage patterns across a large codebase?

Call-path tracing identifies how functions and modules interact, revealing usage patterns and dependencies. Combined with semantic search, it maps the architecture so you understand both the structure and how components communicate.

What's the best way to document architecture findings during codebase exploration?

Document findings by combining symbol extraction and pattern discovery into architecture plans stored persistently. This creates reference material for future onboarding and investigations without repeating exploration work.

How does semantic search help when onboarding to a new codebase?

Semantic search locates relevant code and architecture components quickly without memorizing file names or structure, accelerating onboarding by connecting queries to actual implementations and design decisions.

Do I need to manually map codebase structure, or can this be automated?

Automated symbol extraction and call-path tracing generate codebase maps without manual charting. Checkpointing preserves these maps, eliminating redundant exploration across multiple investigations.