map-project

Generate a system architecture document covering file structure, APIs, data models, and integrations.

Updated Mar 12, 2026
One-click install
npx skills add https://github.com/sogadaiki/claude-code-skills --skill map-project
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: map-project
Source: https://github.com/sogadaiki/claude-code-skills/tree/main/skills/map-project
Command: npx skills add https://github.com/sogadaiki/claude-code-skills --skill map-project

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill addresses the critical issue of project-wide understanding and alignment by systematically investigating and documenting the complete project landscape, preventing misinterpretations and ensuring a shared, up-to-date knowledge base.

Core Features & Use Cases

  • Comprehensive Documentation: Gathers information on file structure, APIs, data models, external integrations, authentication, data flow, and project history.
  • Contextual Interviews: Conducts targeted interviews to capture human factors, relationships, motivations, and potential pitfalls that are not evident from files alone.
  • Multi-Agent Investigation: Utilizes three specialized "Explore" agents to conduct parallel, independent investigations for thoroughness.
  • Use Case: Before onboarding a new team member or starting a major refactor, run /map-project to generate a definitive system architecture document that serves as the single source of truth, ensuring everyone is on the same page.

Quick Start

Run the map-project skill on the current directory to document its entire landscape.

Frequently Asked Questions about map-project

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

FAQPage Schema
How do I generate a system architecture document for an existing codebase?

To generate a system architecture document, you can run an automated project mapping process that investigates file structure, APIs, data models, and data flow. It outputs a comprehensive markdown file storing the entire project landscape as a single source of truth.

What is the best way to document project history and external integrations for team onboarding?

Documenting project history and external integrations is best handled by multi-agent codebase analysis. It investigates the complete landscape and captures human factors via contextual interviews, ensuring new team members receive a definitive, up-to-date project overview.

Can I automatically detect project type and update existing documentation?

Yes, you can automatically detect project type and update existing documentation. The mapping process supports differential updates, ensuring your system architecture document reflects recent changes without rewriting the entire project knowledge base.

How does contextual interviewing improve codebase analysis and knowledge management?

Contextual interviewing improves codebase analysis by capturing human factors, relationships, and motivations not evident in files alone. This enriches knowledge management by adding context to data flow and system architecture details, preventing misinterpretations.

Does this project mapping approach work for legal or business plan projects?

Yes, this project mapping approach works for legal or business plan projects. It systematically investigates and documents the entire landscape of software, legal, or business plans, ensuring shared alignment and a comprehensive knowledge base across domains.