discover

Analyze repository architecture and generate docs/system-map.md with dependencies and risks.

Updated Mar 19, 2026

Search Tags:#architecture #documentation #discovery #evidence #handoff #analyze #system-map

Ready to run

npx skills add https://github.com/espensev/ai-skills --skill discover-espensev

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: discover
Source: https://github.com/espensev/ai-skills/tree/main/gemini-skills/skills/discover
Command: npx skills add https://github.com/espensev/ai-skills --skill discover-espensev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams generate a formal system-map from a repository analysis, clarifying architecture and dependencies to enable better planning and handoff.

Core Features & Use Cases

Generate a top-level Topological Map of subsystems, files, and dependencies.
Produce a Current State narrative describing how the system currently works and integrates components.
Identify risks and open questions to surface gaps and potential failure points.

Quick Start

Ask the Discover Agent to analyze the target repository and generate docs/system-map.md.

Frequently Asked Questions about discover

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

FAQPage Schema

How do I generate architecture documentation from a codebase for project handoff?▼

To generate architecture documentation for project handoff, you can use a system-map approach that analyzes a repository to produce a single docs/system-map.md file. This artifact documents top-level components, dependencies, risks, and open questions with source evidence.

What is a topological map of subsystems and dependencies in a software repository?▼

A topological map of subsystems and dependencies is a structural representation identifying top-level components, their files, and how they integrate within a software repository. It serves as evidence-driven architecture documentation for planning and handoff.

Can I analyze read-only codebases of varying sizes to map subsystems and dependencies?▼

Yes, you can analyze read-only codebases of varying sizes to map subsystems, files, dependencies, risks, and open questions. The process identifies repository architecture and produces a system-map artifact for handoff without requiring write access.

How do I document current state and identified risks for a codebase handoff?▼

To document current state and identified risks for a codebase handoff, generate a system-map artifact containing a Current State narrative and an Identified Risks section. This documentation surfaces gaps and potential failure points with source evidence.

What's the best way to turn repository analysis into a system map with source evidence?▼

The best way to turn repository analysis into a system map with source evidence is to apply an evidence-driven discovery process that outputs a single docs/system-map.md file. This artifact includes a Topological Map, Current State, Identified Risks, Open Questions, and Source Evidence.

Why does system mapping include open questions when analyzing a repository architecture?▼

System mapping includes open questions when analyzing repository architecture to surface gaps and potential failure points that require further investigation. This evidence-driven approach ensures the generated docs/system-map.md artifact delivers comprehensive handoff documentation.