Which documentation files does this skill generate?

It generates 9 files: Functional Specification, Integration Points, Configuration Reference, Data Architecture, Operations Guide, Technical Debt Analysis, Observability Requirements, Visual Design System, and Test Documentation.

What is the difference between Greenfield and Brownfield paths?

Greenfield path extracts framework-agnostic business logic (the 'what') for rebuilding on a new stack, while Brownfield documents the full technical implementation (the 'how') for maintaining or migrating the existing stack.

What are the prerequisites for using the reverse-engineer skill?

You must have completed Step 1 (Initial Analysis) and generated an analysis-report.md file with a selected project path (Greenfield or Brownfield).

Is this skill compatible with monorepos?

Yes, it includes specific detection and extraction logic for Monorepo Services and Nx Applications, identifying shared packages and project-specific configurations.

How long does the reverse engineering process take?

Depending on the complexity of the codebase, the automated deep analysis and documentation generation typically takes between 30 to 45 minutes.

StackShift Codebase Reverse Engineering

Name: StackShift Codebase Reverse Engineering
Author: jschulte

byjschulte

•

学習とドキュメンテーション

Analyzes existing codebases to generate comprehensive documentation for business logic, technical implementation, and system architecture.

StackShift Codebase Reverse Engineering

byjschulte

•

学習とドキュメンテーション

Analyzes existing codebases to generate comprehensive documentation for business logic, technical implementation, and system architecture.

概要

This skill automates the second step of the StackShift workflow by performing a deep dive into existing applications to extract essential domain knowledge. It adapts its analysis based on project goals—focusing on tech-agnostic business logic for Greenfield rewrites or capturing the full technical stack for Brownfield migrations. By generating nine standardized documentation files covering API contracts, infrastructure, and test coverage, it provides the structural foundation required to transition from legacy code to spec-driven development.

主な機能

Deep codebase analysis across backend, frontend, and infrastructure layers
1 GitHub stars
Path-aware extraction modes for Greenfield (business-only) or Brownfield (technical) projects
Discovery of API endpoints, environment variables, and external service dependencies
Detailed identification of technical debt and refactoring opportunities
Automated generation of 9 comprehensive documentation files including functional specs and data architecture

ユースケース

Performing a comprehensive technical audit to identify security gaps and performance bottlenecks
Documenting an undocumented legacy codebase before a major migration or handoff
Extracting core business logic from a monorepo to prepare for a tech stack transition

概要

主な機能

Deep codebase analysis across backend, frontend, and infrastructure layers
1 GitHub stars
Path-aware extraction modes for Greenfield (business-only) or Brownfield (technical) projects
Discovery of API endpoints, environment variables, and external service dependencies
Detailed identification of technical debt and refactoring opportunities
Automated generation of 9 comprehensive documentation files including functional specs and data architecture

ユースケース

Performing a comprehensive technical audit to identify security gaps and performance bottlenecks
Documenting an undocumented legacy codebase before a major migration or handoff
Extracting core business logic from a monorepo to prepare for a tech stack transition