plan-cartography

Build and analyze code graphs from git-kb code JSON.

Updated Jun 2, 2026
One-click install
npx skills add https://github.com/FlexNetOS/envctl --skill plan-cartography
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-cartography
Source: https://github.com/FlexNetOS/envctl/tree/main/.agents/skills/plan-cartography
Command: npx skills add https://github.com/FlexNetOS/envctl --skill plan-cartography

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git-kb code, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill turns a target subsystem into a persistent code graph, providing graph-intelligence and aiding in planning processes.

Core Features & Use Cases

  • Code Graph Creation: Materializes code into a graph and derives intelligence from it.
  • Graph-Intelligence Metrics: Calculates centrality, blast-radius, dead code, cycles, layering-violations, and public-API surface.
  • Persistent and Versioned Graph: Snapshots the graph each cycle and diff against the previous version.
  • Use Case: For a new project, use this Skill to map the codebase, identify hotspots, and plan the architecture.

Quick Start

Run the 'plan-cartography' skill on the 'secrets-proto' target to build its code graph.

Frequently Asked Questions about plan-cartography

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

FAQPage Schema
How do I build a code graph for software architecture planning?

To build a code graph for software architecture planning, you materialize a target subsystem into a persistent graph using indexed JSON data. This process derives graph-intelligence to aid in mapping dependencies and identifying structural hotspots.

Can I detect dependency cycles and layering violations in my codebase?

Yes, you can detect dependency cycles and layering violations by applying graph-intelligence metrics to your code graph. This analysis also calculates centrality, blast-radius, dead code, and the public-API surface.

Do I need git-kb code to perform codebase dependency mapping?

Yes, you need the git-kb code dependency for codebase dependency mapping because it provides the required JSON indexing and querying. The code graph is built and analyzed directly from this JSON output.

What is code graph intelligence and how does it assess risk?

Code graph intelligence assesses risk by calculating metrics like centrality and blast-radius from a materialized code graph. It identifies structural hotspots and dead code to support architecture planning and risk assessment.

How do I track architecture changes across different code versions?

To track architecture changes across different code versions, snapshot the code graph each cycle and diff it against the previous version. This persistent and versioned graph approach highlights evolving dependency mappings and structural shifts.