project-explore

name	project-explore
description	Systematically explore and document an unfamiliar codebase by following a structured analysis pipeline. Use this skill when a user asks to explore, analyze, understand, or document an unfamiliar project or codebase.

Project Explore

Systematically analyze an unfamiliar codebase through five structured phases and persist findings to .docs/.

Analysis Pipeline

Execute each phase in order. After completing each phase, save the output to the corresponding file under .docs/ (create the directory if absent).

Phase	Output file
1. System Boundary	.docs/01-system-boundary.md
2. Core Concepts	.docs/02-concepts.md
3. Architecture Design	.docs/03-architecture.md
4. Core Abstractions	.docs/04-abstractions.md
5. Critical Perspective	.docs/05-critical-perspective.md

After all five phases: generate .docs/index.md - a concise overview that links to the five documents.

See references/prompts.md for the exact analysis prompts in Chinese for each phase.

Output Format per Phase

Each .docs/ file should follow this structure:

# [Phase Name]

> One-sentence summary of the findings.

## [Sub-section per question answered]

...content...

index.md Format

# Project Analysis Index

> One-paragraph executive summary of the entire project.

## Documents

| # | Topic | File | Summary |
|---|-------|------|---------|
| 1 | System Boundary | [01-system-boundary.md](01-system-boundary.md) | ... |
| 2 | Core Concepts | [02-concepts.md](02-concepts.md) | ... |
| 3 | Architecture Design | [03-architecture.md](03-architecture.md) | ... |
| 4 | Core Abstractions | [04-abstractions.md](04-abstractions.md) | ... |
| 5 | Critical Perspective | [05-critical-perspective.md](05-critical-perspective.md) | ... |

## Key Takeaways

- ...