skills.rest
SergeuMatyasov
SergeuMatyasovCOMMUNITY
Explore all skills by this author →
GitHub

module-analysis-template

Document module analysis points and dependency maps for migration planning.

Updated Apr 9, 2026
Search Tags:#architecture#analysis#migration#decomposition#module#dependency-map
One-click install
npx skills add https://github.com/SergeuMatyasov/dotnet-shared-skills --skill module-analysis-template
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: module-analysis-template
Source: https://github.com/SergeuMatyasov/dotnet-shared-skills/tree/main/module-analysis-template
Command: npx skills add https://github.com/SergeuMatyasov/dotnet-shared-skills --skill module-analysis-template

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured approach to analyze files and modules before migration, decomposition, and layering, ensuring clear ownership and boundaries.

Core Features & Use Cases

  • Analyze each file or module individually to capture responsibilities, inputs, outputs, dependencies, side effects, hidden invariants, and layering context.
  • Produce a single table that documents domain, application, and infrastructure concerns, and identifies the point of coupling with legacy systems.
  • Build a dependency map to guide migration planning and modularization, enabling safer refactors and easier future maintenance.

Quick Start

Provide a target module and fill out the analysis table for each file or module using the template.

Frequently Asked Questions about module-analysis-template

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

FAQPage Schema
How do I analyze module dependencies before a codebase migration?▼

Module analysis for migration involves documenting each file's responsibilities, inputs, outputs, dependencies, and side effects. You generate a dependency map to separate domain, application, and infrastructure concerns, ensuring safer refactoring and clear boundaries.

What is the best way to map hidden invariants and layering boundaries for decomposition?▼

Mapping hidden invariants and layering boundaries requires analyzing each module individually to document side effects and coupling points. Applying a structured template separates concerns to guide modularization and identify legacy system coupling.

How do I document legacy system coupling points during architecture analysis?▼

Document legacy system coupling points by applying a template to each file to capture dependencies and layering context. This produces a single table separating domain, application, and infrastructure concerns for migration planning.

How do I handle unconfirmed dependencies when building a module dependency map?▼

When building a module dependency map, handle unconfirmed dependencies by marking them as 'не подтверждено'. Ensure all documented facts are supported by code or tests, and maintain a dedicated plan for resolving these unknowns.

Can I use a structured template to separate domain and infrastructure concerns for migration planning?▼

Yes, you can use a structured template to separate domain, application, and infrastructure concerns for migration planning. The template captures responsibilities and side effects for each module, producing a consistent dependency map.

Related Skills

Explore More Software Engineering Skills→
C0ntr0lledCha0sC0ntr0lledCha0s
8

documentation-writer

Generate module READMEs, user guides, and technical references from source code.

Community
Basic
starrank-softstarrank-soft

hexagonal-architecture

Implement ports and adapters to decouple business logic across TypeScript, Java, Kotlin, and Go.

Official
Advanced
julianobarbosajulianobarbosa
7

reviewing-code

Review code for quality, bugs, security issues, and best practices using Codex.

Community
Advanced
nsalvacaonsalvacao

Architecture Coherence

Detect architecture drift by comparing declared architecture with actual code structure and dependencies.

Community
Advanced