product-reverse-engineer

Analyze existing software projects to generate product overviews, functional specifications, and technical design documents.

Updated Jan 28, 2026
One-click install
npx skills add https://github.com/scanady/forge-agents --skill product-reverse-engineer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: product-reverse-engineer
Source: https://github.com/scanady/forge-agents/tree/main/skills/product-reverse-engineer
Command: npx skills add https://github.com/scanady/forge-agents --skill product-reverse-engineer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill addresses the challenge of understanding and documenting complex existing software projects, enabling accurate planning for future development or complete rewrites.

Core Features & Use Cases

  • Comprehensive Analysis: Deeply explores codebases to map architecture, domain models, features, and integrations.
  • Product-Agnostic Documentation: Generates clear Product Overviews, Functional Specifications, and Technical Design Documents, free from proprietary jargon.
  • Use Case: A company needs to rebuild a legacy system but lacks up-to-date documentation. This Skill can analyze the existing codebase and produce the necessary documentation to guide the greenfield development process.

Quick Start

Use the product-reverse-engineer skill to document the project located at '/path/to/existing/project'.

Frequently Asked Questions about product-reverse-engineer

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

FAQPage Schema
How do I generate technical design documentation from an existing codebase?

You can reverse engineer a legacy codebase by analyzing the existing software to capture system architecture, domain models, and features, generating product-agnostic documentation that guides your greenfield development process.

How do I extract system architecture and domain models from existing source code?

Reverse engineering existing software for greenfield development involves analyzing the codebase to produce a functional specification and technical design document, capturing all necessary details to accurately plan a complete rewrite.

Can I use this to create functional specs from an undocumented legacy system?

To reverse engineer a legacy codebase, you analyze the existing software to capture system architecture, domain models, and features, generating product-agnostic documentation that guides your greenfield development process.

What's the best way to document a software project for a complete rewrite?

To generate technical design documentation from an existing codebase, the skill analyzes your project to extract system architecture, domain models, and integrations, producing a comprehensive technical design document for greenfield rebuilding.

Does this generate product-agnostic documentation free from proprietary jargon?

Extracting system architecture and domain models from source code involves deeply exploring the codebase to map features and integrations, resulting in product-agnostic documentation including a product overview and functional specification.

Why do I need to analyze integrations and security details when reverse engineering a project?

Yes, you can create functional specs from an undocumented legacy system by analyzing the existing software project to generate comprehensive, product-agnostic documentation that captures features, security, and deployment details.