aggregate-platform-architecture

Aggregate component architecture summaries into a platform-level Markdown document.

Updated Apr 1, 2026
One-click install
npx skills add https://github.com/jctanner/platform-architecture-context-pipeline --skill aggregate-platform-architecture
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aggregate-platform-architecture
Source: https://github.com/jctanner/platform-architecture-context-pipeline/tree/main/.claude/skills/aggregate-platform-architecture
Command: npx skills add https://github.com/jctanner/platform-architecture-context-pipeline --skill aggregate-platform-architecture

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Combine multiple component architecture summaries into a platform-level architecture document to provide a wholistic, easy-to-navigate view of the entire system.

Core Features & Use Cases

  • Aggregates component-level architectures into a single PLATFORM.md, enabling holistic platform visibility.
  • Supports both organized architecture directories and legacy repos-dir workflows, allowing flexible aggregation from distributed sources.
  • Generates a platform-level summary document for architecture reviews, SAR documentation, and onboarding.

Quick Start

Run /aggregate-platform-architecture --platform=<name> --version=<version> after component architectures have been collected.

Frequently Asked Questions about aggregate-platform-architecture

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

FAQPage Schema
How do I combine multiple component architecture summaries into a single platform document?

You can aggregate component architecture summaries into a unified platform-level document by consolidating individual component maps, dependencies, and namespaces into a single Markdown file providing holistic system visibility.

What is the best way to generate a platform-level architecture report from distributed component docs?

Generating a platform-level architecture report involves consolidating distributed component docs into a unified Markdown file, consolidating architecture tables and detailing dependencies and services for platform-wide visibility.

How do I consolidate architecture tables and namespaces for an architecture review?

Consolidating architecture tables and namespaces for reviews requires aggregating component summaries into a holistic PLATFORM.md document, detailing system dependencies and services for easy navigation.

Can I aggregate platform architecture from legacy repos directories instead of organized architecture directories?

Yes, platform architecture aggregation supports both organized architecture directories and legacy repos-dir workflows, allowing flexible collection of component summaries from distributed sources into a single document.

Do I need component architecture summaries collected before generating a platform-level architecture document?

Yes, you need component architecture summaries collected from the collection step before aggregating them, as the workflow unifies existing component maps into a platform-wide Markdown report.

Why does aggregating component architectures into one document help with onboarding?

Aggregating component architectures into one document helps onboarding by providing a unified, easy-to-navigate platform view that consolidates dependencies, namespaces, and services into a single Markdown report.