pm-context-scan-codebase

Name: pm-context-scan-codebase
Availability: InStock
Author: pingmepi

Scan a codebase to generate a structured markdown summary of architecture, features, and technical debt.

Updated Jun 8, 2026

Search Tags:#architecture #documentation #codebase #analysis #product-management #tech-debt

Ready to run

npx skills add https://github.com/pingmepi/pm-os --skill pm-context-scan-codebase

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: pm-context-scan-codebase
Source: https://github.com/pingmepi/pm-os/tree/main/skills/pm-context-scan-codebase
Command: npx skills add https://github.com/pingmepi/pm-os --skill pm-context-scan-codebase

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the information asymmetry between product managers and technical codebases by automatically generating a structured, high-level overview of the project's architecture, features, and tech debt.

Core Features & Use Cases

Automated Discovery: Scans project files to map entry points, data models, and integration points without manual code review.
Structured Documentation: Produces a standardized 00-codebase-understanding.md file that serves as a single source of truth for product planning.
Use Case: Use this skill when starting a new project or taking over an existing codebase to quickly identify the tech stack, key modules, and potential technical debt before drafting a product brief.

Quick Start

Run the pm-context-scan-codebase skill to analyze the current directory and generate a structured codebase understanding document.

Frequently Asked Questions about pm-context-scan-codebase

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

FAQPage Schema

How do I analyze an existing codebase for product planning without reading code manually?▼

To analyze an existing codebase for product planning without manual code review, run an automated read-only scan that maps entry points, data models, and integration points to generate a structured markdown summary of architecture and features.

What is the best way to identify technical debt before taking over an existing software project?▼

The best way to identify technical debt before taking over an existing software project is to perform an exploratory codebase scan that evaluates the repository manifest files and maps the feature surface to expose potential structural weaknesses.

Can I generate architecture documentation automatically from standard repository manifest files?▼

Yes, you can generate architecture documentation automatically by running a read-only scan that requires standard repository manifest files and project root read access to map the data layer and output a standardized markdown file.

How does automated codebase discovery work for product managers?▼

Automated codebase discovery works for product managers by scanning project files to extract the tech stack, key modules, and integration points, producing a single source of truth markdown document that grounds enhancement plans in technical reality.

Does codebase analysis require write access to the project root directory?▼

No, codebase analysis does not require write access; it operates as a strictly read-only exploratory scan of the project root directory to ensure the existing codebase remains unmodified during the discovery phase.

What limitations exist when scanning a codebase to map features and data models?▼

Limitations when scanning a codebase include relying entirely on standard repository manifest files to map features and data models, meaning projects lacking standard manifests may not produce a complete architectural summary.