agentic-architecture

Diagnose codebase architecture using coordinated multi-agent analysis and evidence-based reports.

92|9|Updated Mar 14, 2026
One-click install
npx skills add https://github.com/Ovid/paad --skill agentic-architecture
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agentic-architecture
Source: https://github.com/Ovid/paad/tree/main/plugins/paad/skills/agentic-architecture
Command: npx skills add https://github.com/Ovid/paad --skill agentic-architecture

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Diagnose architectural quality of a codebase by coordinating specialist agents to identify structure, coupling, data ownership, integration patterns, and evidence-based flaws.

Core Features & Use Cases

  • Phase-driven reconnaissance and parallel specialist analysis to produce a balanced, evidence-backed architecture report.
  • Scope-flexible evaluation across single modules or multi-service repositories to reveal boundaries, dependencies, and risks.
  • Evidence-rich reporting that documents findings with concrete file paths, excerpts, and impact assessments for architecture reviews.

Quick Start

Run the agentic-architecture skill on your repository to start the phased analysis and generate an architecture report.

Frequently Asked Questions about agentic-architecture

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

FAQPage Schema
How do I perform an architecture review on a large monorepo?

Multi-agent architecture analysis works by dispatching domain-focused agents to perform parallel reconnaissance, verifying findings, and generating an evidence-backed report on structure, coupling, data ownership, and integration patterns.

How do I identify coupling and dependency risks across multiple services?

Multi-agent architecture analysis works by dispatching domain-focused agents to perform parallel reconnaissance, verifying findings, and generating an evidence-backed report on structure, coupling, data ownership, and integration patterns.

What is multi-agent architecture analysis and how does it work?

Multi-agent architecture analysis works by dispatching domain-focused agents to perform parallel reconnaissance, verifying findings, and generating an evidence-backed report on structure, coupling, data ownership, and integration patterns.

Can I evaluate the architecture of a single module, or does it only work on multi-service repositories?

Architecture evaluation is scope-flexible and can be applied to both single modules and multi-service repositories to reveal boundaries, dependencies, and resilience concerns using the same coordinated multi-agent analysis.

What is the best way to generate an evidence-rich architecture report for a codebase?

The best way to generate an evidence-rich architecture report is to run phased multi-agent analysis that documents structural findings with concrete file paths, excerpts, and risk assessments for comprehensive architecture reviews.

When should I not use a multi-agent approach for system design analysis?

Multi-agent system design analysis targets large repositories or monorepos hosting multiple services; it may be excessive for evaluating very small codebases where manual inspection of structure and boundaries is still feasible.