architecture-extract

Identify module boundaries, data flows, and service interactions from codebase trees.

Updated Mar 8, 2026
One-click install
npx skills add https://github.com/petrSimonidesXart/xPmGateway --skill architecture-extract-petrsimonidesxart
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architecture-extract
Source: https://github.com/petrSimonidesXart/xPmGateway/tree/main/.gaai/core/skills/cross/architecture-extract
Command: npx skills add https://github.com/petrSimonidesXart/xPmGateway --skill architecture-extract-petrsimonidesxart

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Convert raw project structure into clear architectural understanding — identify module boundaries, data flows, and service relationships to enable memory ingestion and design discussions.

Core Features & Use Cases

  • Analyze module boundaries and layering to reveal system structure.
  • Identify data flows and service interactions to map dependencies.
  • Detect architectural patterns (monolith, microservices, event-driven) and produce a concise architecture summary for documentation and onboarding.

Quick Start

Run architecture-extract after a codebase-scan to generate architecture insights.

Frequently Asked Questions about architecture-extract

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

FAQPage Schema
How do I map codebase architecture and identify module boundaries from a project structure?

Mapping codebase architecture involves analyzing module boundaries, data flows, and service interactions within a project structure. This reveals the underlying architecture, detecting patterns like monolith, microservices, or event-driven structures for clear understanding.

What is the best way to detect architectural patterns like microservices or event-driven structures in my codebase?

Detecting architectural patterns involves scoping analysis to the codebase tree and key files list to identify service interactions and data flows. This maps the system structure and detects monolith, microservices, or event-driven architectures.

How do I generate architecture insights suitable for memory ingestion?

Generate architecture insights by analyzing module boundaries and layering, then encoding findings into an architecture insights artifact. This output captures service relationships and data flows, making the architecture suitable for memory-ingest and onboarding.

Can I analyze service interactions and data flows using only a codebase tree and key files list?

Yes, you can analyze service interactions and data flows by scoping the analysis specifically to a provided codebase tree and key files list. This targeted approach identifies service relationships and maps dependencies without scanning the entire codebase.

Does architecture extraction work without running a prior codebase scan?

Architecture extraction requires a prior codebase scan to provide the necessary codebase tree and key files list. Running it after a codebase-scan ensures the accurate identification of module boundaries, data flows, and architectural patterns.