Architectural Baseline Diagnoser

Diagnose a repository's architectural style by analyzing dependency manifests, directory structures, and code patterns.

2|Updated Jun 24, 2026
One-click install
npx skills add https://github.com/Hypercart-Dev-Tools/pdda --skill architectural-baseline-diagnoser
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Architectural Baseline Diagnoser
Source: https://github.com/Hypercart-Dev-Tools/pdda/tree/main/PROJECT/4-MISC/OPINIONATED-ARCHITECTURE
Command: npx skills add https://github.com/Hypercart-Dev-Tools/pdda --skill architectural-baseline-diagnoser

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill removes the guesswork from project documentation by objectively diagnosing the actual architectural patterns currently in use within a repository, rather than relying on outdated or aspirational descriptions.

Core Features & Use Cases

  • Evidence-Based Diagnosis: Analyzes dependency manifests, directory structures, and code patterns to identify the dominant architectural camp.
  • Standardized Documentation: Automatically generates a clear, falsifiable Architectural Baseline section for your AGENTS.md file.
  • Use Case: Use this when onboarding a new team member or starting a refactor to ensure everyone understands the current system constraints and guiding principles before making changes.

Quick Start

Run the architectural baseline diagnoser to analyze the current repository and append the findings to the AGENTS.md file.

Frequently Asked Questions about Architectural Baseline Diagnoser

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

FAQPage Schema
How do I diagnose the architecture of an existing software repository?

To diagnose software architecture, this skill analyzes dependency manifests, directory structures, and code patterns to objectively identify the dominant architectural style currently in use within your repository.

What is the best way to document code architecture for new team onboarding?

Documenting code architecture for onboarding is best handled by generating a falsifiable Architectural Baseline section, ensuring new members understand actual system constraints and guiding principles rather than relying on aspirational descriptions.

How do I prepare a repository for a major refactoring project?

Preparing a repository for refactoring requires establishing an evidence-based architectural baseline, which audits current code patterns and directory structures to clarify existing constraints before making structural changes.

Can I automatically generate architecture documentation for my agents?

Yes, you can generate architecture documentation for agents by running the diagnoser to analyze your repository and automatically append the objective findings directly into your AGENTS.md file.

Does this architecture analysis tool require any external dependencies?

No, this architecture analysis tool operates without external dependencies, directly inspecting your repository's manifests and directory structures to produce baseline documentation.

Why should I use evidence-based architecture diagnosis instead of relying on existing documentation?

Evidence-based architecture diagnosis removes guesswork by analyzing actual code patterns, ensuring your baseline documentation reflects current system realities instead of outdated or aspirational project descriptions.