---
name: Architecture Extract
slug: architecture-extract
category: AI Engineering
description: Architecture Extract turns a scanned codebase into a concise view of module boundaries, data flows, service relationships, and the architectural pattern. Use it during bootstrap before memory ingestion.
github: "https://github.com/digipulse-engineering/GAAI-framework/tree/main/.gaai/core/skills/cross/architecture-extract"
language: Shell
stars: 161
forks: 27
install: "npx degit https://github.com/digipulse-engineering/GAAI-framework/tree/main/.gaai/core/skills/cross/architecture-extract ~/.claude/skills/architecture-extract"
installs_to: ~/.claude/skills/architecture-extract
source_path: .gaai/core/skills/cross/architecture-extract/SKILL.md
collection_size: 25
category_size: 3670
collection_url: "https://dirskills.com/collections/Fr-e-d/GAAI-framework"
added: 2026-09-08T05:36:19.062Z
last_synced: 2026-09-08T05:36:19.062Z
canonical_url: "https://dirskills.com/skills/architecture-extract"
---

# Architecture Extract

Architecture Extract turns a scanned codebase into a concise view of module boundaries, data flows, service relationships, and the architectural pattern. Use it during bootstrap before memory ingestion.

**Install:**

```bash
npx degit https://github.com/digipulse-engineering/GAAI-framework/tree/main/.gaai/core/skills/cross/architecture-extract ~/.claude/skills/architecture-extract
```

## README

# Architecture Extract

## Purpose / When to Activate

Activate:
- After `codebase-scan` during Bootstrap initialization
- When architectural understanding is needed before memory ingestion

---

## Process

1. Analyze module boundaries and layering
2. Identify data flow and service interactions
3. Detect architectural patterns (monolith, services, event-driven, etc.)
4. Produce a concise architecture summary

---

## Outputs

**`architecture_insights`** — concise summary including:
- System structure overview
- Module boundaries and responsibilities
- Key data flows
- Architectural pattern identified
- Major dependencies
- Notable constraints or risks

---

## Quality Checks

- System structure is understandable in one view
- Major dependencies are explicit
- Architecture style is clearly identified
- Output is suitable for ingestion via `memory-ingest`

---

## Non-Goals

This skill must NOT:
- Make architectural recommendations
- Propose changes
- Read deeply into implementation details

**Converts terrain map into architectural understanding. Feeds directly into memory-ingest.**