doc

Generate CODEMAPS and HUMANMAPS documentation from codebase structure.

1|Updated Mar 6, 2026
One-click install
npx skills add https://github.com/SeoJaeWan/try-claude-code --skill doc-seojaewan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: doc
Source: https://github.com/SeoJaeWan/try-claude-code/tree/main/plugin/develop/skills/doc
Command: npx skills add https://github.com/SeoJaeWan/try-claude-code --skill doc-seojaewan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

CODEMAPS and HUMANMAPS auto-generation scans service code structure and outputs documentation to codemaps/ and humanmaps/. Use when the user asks to update or regenerate project documentation, or after significant code changes.

Core Features & Use Cases

  • Auto-detects service roots and builds codemaps and humanmaps for documentation
  • Integrates with the plan orchestrator to update docs after changes
  • Works across monorepos and single repos to produce architecture and API doc maps
  • Use Case: When major refactors occur, quickly regenerate all docs to reflect current state.

Quick Start

Trigger the doc-update workflow to regenerate CODEMAPS and HUMANMAPS for the current project.

Frequently Asked Questions about doc

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

FAQPage Schema
How do I auto-generate documentation after major code refactoring?

Auto-generate documentation after code refactoring by triggering the doc-update workflow to scan service roots, detect changes, and extract structure into updated codemaps and humanmaps.

What are CODEMAPS and HUMANMAPS in a codebase?

CODEMAPS and HUMANMAPS are documentation outputs generated by scanning codebase structure, representing architecture and API doc maps stored under the codemaps/ and humanmaps/ directories.

Does automated documentation generation work with monorepo projects?

Automated documentation generation works across both monorepos and single repos, detecting service roots to produce architecture and API doc maps for multi-repo or monorepo projects.

How do I refresh project documentation to reflect current code state?

Refresh project documentation by running the doc-update workflow, which performs scan-for-roots and change detection to output updated CODEMAPS and HUMANMAPS reflecting the current state.

What is the best way to maintain architecture docs across multiple repositories?

Maintain architecture docs across multiple repositories by using automated codebase scanning to detect service roots and regenerate all CODEMAPS and HUMANMAPS on-demand after changes.