software-architecture-analysis
Use this skill to reverse-engineer an existing software system, map its architecture, data flow, privacy posture, coupling, quality characteristics, and feature surface, then produce an evidence-grounded clean-room design document, PRD, or migration plan under new constraints. Use for codebase archaeology, implicit contract extraction, architecture health assessment, or decomposition-readiness analysis. Do not use for greenfield architecture design, direct code review, bug hunting, security auditing, or implementation of API, data, platform, or migration changes; route those to the relevant neighboring skill.
Target: Office & team collaboration. Automatically collected · unverified.
Excerpt from the author’s documentation
Extracted from a fixed version of SKILL.md in its original language. This is the author’s documentation; installation, compatibility and runtime results have not been verified by this site.
Read the original English text
Topics in the source
- Software Architecture Analysis — Codebase Reverse Engineering to Design Document
- When to Use
- Build Workflow
- Phase 1: Repository Cloning and Structure Mapping
- Phase 2: Identify Key Architectural Files
- Phase 3: Architecture Mapping
- Architecture evidence lenses
- Phase 3b: Interface Extraction Pattern (DAO/Provider Contract Design)
A reference implementation exists and you need to understand its architecture for design inspiration You need a PRD, design document, or specification for a system in the same problem space The output must be clean-room: zero source code samples copied from the reference codebase You're designing a system with different architectural constraints (local-first, privacy-first, self-hosted) than the reference You need to extract an implicit contract — the storage operations a codebase performs — to design a formal provider abstraction You need to assess architecture health, coupling, modularity, data ownership, distributed workflows, or readiness for a boundary change from repository evidence Don't use for: Greenfield or proactive architecture design (route to software-architecture), direct code review, bug hunting, or security auditing. Route API/interface semantics to api-design-and-evolution, data-platform strategy to data-architect, implementation to the relevant engineering skill, deployment substrate to platform-engineering, and execution of an approved cross-system migration to migration-engineering. Clone the target repository with a shallow clone: Map the top-level directory s
This is an excerpt. Refer to the complete source and its current requirements.
- Source repository
- OKHP3/skillz
- Source file
- community/software-architecture-analysis/SKILL.md
- Fixed revision
- 7b187777d42ab7bc7bab1e5f2c940cd3139ecebf
Sources and evidence
This record was collected automatically. Its documentation, suitability and runtime behavior have not been manually verified.
Author: OKHP3/skillz · original repository metadata. Documentation review: Not reviewed. Last source check: 2026-11-10T10:00:54.347Z.
Categories are inferred from names, descriptions and paths. They do not establish compatibility.
License and attribution
MIT. Third-party content and copyright remain with their authors. Refer to the original license and terms.
Original license ↗Synchronization, copying and user-reported success do not mark a resource as runtime-tested.
Limitations and notes
- Collecting metadata does not mean this site has installed, adapted, runtime-tested or security-reviewed the resource.