product-spec-reverse-engineer

Analyze existing codebases to produce product-agnostic documentation.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Existing codebases often lack concise, product-agnostic documentation that explains architecture, data flows, and capabilities, hindering greenfield rebuilds.

Core Features & Use Cases

  • Generates a complete, product-agnostic set of documents from an existing project: executive overview, functional specification, and technical design.
  • Identifies system scope, key domain entities, external integrations, and security considerations to guide architecture decisions.
  • Produces structured outputs that can be consumed by engineering teams for planning and implementation.

Quick Start

Provide the path to the project root and I will analyze it to produce a product overview, functional specification, and technical design document.

Frequently Asked Questions about product-spec-reverse-engineer

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

FAQPage Schema
How do I generate technical documentation from an existing codebase for a greenfield rebuild?

To generate technical documentation from an existing codebase, you provide the project root path to produce a product-agnostic product overview, functional specification, and technical design document abstracting away product specifics for greenfield rebuilding.

What is product-agnostic documentation and when do I need it for reverse engineering?

Product-agnostic documentation abstracts away specific product names and environment details to explain core architecture, data flows, and capabilities. You need it for reverse engineering when planning a greenfield rebuild or system design without legacy constraints.

How do I reverse engineer a functional specification and technical design from legacy source code?

You can reverse engineer a functional specification and technical design by analyzing the existing source code to identify system scope, key domain entities, external integrations, and security considerations, delivering structured planning artifacts for engineering teams.

Can I use this to extract architecture and data flow documentation for software projects of any size?

Yes, you can extract architecture and data flow documentation across software projects of varying sizes. The analysis identifies system scope and key domain entities to guide architecture decisions regardless of the overall codebase scale.

What is the best way to discover external integrations and security considerations in an undocumented codebase?

The best way to discover external integrations and security considerations is by performing architecture discovery on the codebase, which identifies these elements and maps them into a structured technical design document for engineering teams.