software-architecture-analysis

Analyze repository architecture and data flows to generate clean-room design documents.

86|9|Updated Jun 5, 2026
One-click install
npx skills add https://github.com/magnus919/hermes-profiles --skill software-architecture-analysis
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: software-architecture-analysis
Source: https://github.com/magnus919/hermes-profiles/tree/main/skills/software-architecture-analysis
Command: npx skills add https://github.com/magnus919/hermes-profiles --skill software-architecture-analysis

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Reverse-engineer a software codebase to understand architecture, data flow, privacy posture, and feature surface — then produce a clean-room design document, PRD, or migration plan that re-imagines the system under new constraints (local-first, privacy-first, self-hosted). Use when you need to understand how a system works from its source code or produce a specification without copying implementation details.

Core Features & Use Cases

  • Map architecture: identify components, data flows, and interfaces from a codebase.
  • Assess privacy posture: outline storage, data pathways, and external dependencies.
  • Output design artifacts: generate a platform-agnostic design document or migration plan for architecture teams.

Quick Start

Clone the target repository, run the analysis workflow, and export a clean-room design document that captures architecture without copying code.

Frequently Asked Questions about software-architecture-analysis

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

FAQPage Schema
How do I reverse-engineer a codebase into a design document?

Reverse-engineering a codebase into a design document involves mapping architectural components, data flows, and privacy considerations from the source code to produce a neutral, clean-room specification suitable for architecture teams.

What is a clean-room design document for software architecture?

A clean-room design document is a technology-agnostic specification that reimagines a system under new constraints like local-first or privacy-first. It describes components, interfaces, data contracts, and non-functional requirements without reproducing the original source code.

How do I assess privacy posture and data flows from an existing codebase?

Assessing privacy posture from an existing codebase requires analyzing storage mechanisms, data pathways, and external dependencies. This identifies how information moves through the system and outlines potential privacy considerations for a new design specification.

Can I generate a migration plan from source code without copying implementation details?

You can generate a migration plan from source code by reverse-engineering the architecture and data flows. The resulting plan reimagines the system under local-first or privacy-first constraints without reproducing the original implementation details.

Does this codebase analysis approach work for producing a platform-agnostic PRD?

This codebase analysis approach works for producing a platform-agnostic PRD by reverse-engineering the repository's feature surface and architectural components. It formulates a neutral product requirements document independent of specific technologies.