skills.rest
netguy204
netguy204COMMUNITY
Explore all skills by this author →
Website𝕏@netguy204GitHub

discover-subsystems

Identify, analyze, and document subsystems from a codebase.

3|1|Updated Jan 8, 2026
Search Tags:#workflow#documentation#migration#code-analysis#subsystems#discover
One-click install
npx skills add https://github.com/netguy204/vibe-engineer --skill discover-subsystems
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: discover-subsystems
Source: https://github.com/netguy204/vibe-engineer/tree/main/.agents/skills/discover-subsystems
Command: npx skills add https://github.com/netguy204/vibe-engineer --skill discover-subsystems

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Subsystem discovery turns opaque codebases into explicit architectural maps, capturing subsystem boundaries and documentation in a repeatable workflow.

Core Features & Use Cases

  • Code analysis to identify subsystems and boundaries.
  • Generation of draft subsystem documentation, questions for clarification, and migration-ready artifacts.
  • Best for architectural discovery in large repos, onboarding teams, and documenting legacy systems.

Quick Start

Run the subsystem discovery workflow to analyze your codebase and generate initial subsystem documentation.

Frequently Asked Questions about discover-subsystems

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

FAQPage Schema
How do I discover and document subsystems in a large legacy codebase?▼

To discover subsystems in a legacy codebase, you can run an automated discovery workflow that analyzes code structure, proposes architectural boundaries, and generates structured subsystem documentation.

What is the best way to identify unclear subsystem boundaries in a monorepo?▼

The best way to identify unclear boundaries in a monorepo is using a discovery workflow that analyzes code dependencies to propose explicit subsystem maps and capture architectural structures.

How does a workflow for architectural discovery handle operator input?▼

An architectural discovery workflow handles operator input by proposing initial subsystem boundaries from code analysis, then refining those proposed subsystems based on your feedback before producing final documentation.

Can I generate migration-ready documentation for architecture onboarding?▼

Yes, you can generate migration-ready subsystem documentation by initiating a discovery workflow that analyzes your codebase and outputs structured artifacts designed for team onboarding and architectural mapping.

Does subsystem discovery work for opaque codebases with no existing documentation?▼

Yes, subsystem discovery works for opaque codebases by analyzing the existing code structure to turn undocumented repositories into explicit architectural maps with repeatable structured documentation.

What are the limitations of using code analysis to map legacy systems?▼

A limitation of using code analysis to map legacy systems is that automated proposals may miss implicit business logic, requiring operator input to refine boundaries and finalize accurate subsystem documentation.

Related Skills

Explore More Software Engineering Skills→
Himanshu040604Himanshu040604

cartographer

Map codebases by orchestrating parallel AI subagents and generate CODEBASE_MAP.md.

Community
Advanced
BlueEventHorizonBlueEventHorizon
5

mermaid-diagram

Generate and validate Mermaid diagrams across seven diagram types.

Community
Intermediate
opensage-agentopensage-agent
113

get-caller

Identify direct and indirect callers of functions using Neo4j callgraph data.

Official
Intermediate
PremModhaOfficialPremModhaOfficial
1

ddd-decomposition

Identify bounded contexts and service boundaries for multi-tenant Go microservices.

Community
Advanced