rpg

Generate a Repository Planning Graph with project, module, and function nodes.

Updated Jan 23, 2026
One-click install
npx skills add https://github.com/Adriftnote/zettelkasten-for-claude --skill rpg-adriftnote
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rpg
Source: https://github.com/Adriftnote/zettelkasten-for-claude/tree/main/.claude/skills/rpg
Command: npx skills add https://github.com/Adriftnote/zettelkasten-for-claude --skill rpg-adriftnote

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams quickly understand and document large codebases by converting source code into a structured Repository Planning Graph (RPG) that maps the hierarchy and relationships across a project.

Core Features & Use Cases

  • Structured mapping of repository: project → module → function/class, with clear containment and relationship lines.
  • RPG Relations automatically generated from code analysis, including contains and calls, enabling traceability.
  • Use Case: On a new codebase, generate a navigable graph to plan modules, estimate effort, and document architecture for onboarding.

Quick Start

Run the rpg-extract on your repository to generate the RPG nodes and relations.

Frequently Asked Questions about rpg

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

FAQPage Schema
How do I document codebase structure and map repository architecture?

To map repository architecture, generate a Repository Planning Graph from source code, producing project, module, and function/class nodes with contains and calls relations for navigable architecture documentation.

What is a repository planning graph and how does it help with code analysis?

A repository planning graph is a structured map of codebase hierarchy and relationships, capturing contains and calls relations between functions and classes to enable traceability and downstream code analysis.

How do I generate a repository planning graph from my source code?

Run the rpg-extract workflow on your repository to generate a repository planning graph, enforcing end-to-end extraction, duplication checks, and context validation to produce nodes and relations.

Can I use this code analysis approach for onboarding to a new codebase?

Yes, this code analysis approach supports onboarding by generating a navigable graph that documents architecture, plans modules, and estimates effort across unfamiliar repository structures.

What's the best way to trace function and class calls across a large repository?

Generating a repository planning graph is the best way to trace calls, automatically extracting contains and calls relations to provide full traceability between modules and functions across the codebase.

Does this repository planning graph approach work without external dependencies?

Yes, the repository planning graph approach operates dependency-free, using internal rpg-extract, vecsearch, and build_context workflows to validate context and extract structure end-to-end.