PRD Reverse Engineer

Audit a codebase and generate a manifest and PRD documentation suite.

2|Updated May 1, 2026
One-click install
npx skills add https://github.com/nikkogibler/MarsFounderIO --skill prd-reverse-engineer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: PRD Reverse Engineer
Source: https://github.com/nikkogibler/MarsFounderIO/tree/main/my-instructions/skills/prd-reverse-engineer
Command: npx skills add https://github.com/nikkogibler/MarsFounderIO --skill prd-reverse-engineer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audits the current codebase and converts existing reality into a structured documentation suite (Manifest + PRDs) to align teams and guide development.

Core Features & Use Cases

  • Automates generation of a system manifest and per-feature PRDs from production reality.
  • Produces a navigable docs/index with references to feature docs and tech stack mappings.
  • Use Case: A new release requires an up-to-date set of PRDs and architecture diagrams derived from live code.

Quick Start

Scan your workspace to generate the system manifest and feature PRDs.

Frequently Asked Questions about PRD Reverse Engineer

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

FAQPage Schema
How do I generate PRDs from an existing codebase?

To generate PRDs from an existing codebase, this Skill audits your workspace to extract production reality and automatically outputs a structured documentation suite. It scans feature modules to create per-feature PRD files without fabricating missing information.

What is the best way to document a monorepo with multiple feature modules?

Documenting a monorepo with multiple feature modules is best handled by applying a deterministic workflow that scans the workspace, builds a system manifest, and generates per-feature PRDs, outputting files under docs/ with a final INDEX.md.

Can I reverse engineer code into a system manifest and architecture docs?

Yes, you can reverse engineer code into a system manifest and architecture docs. The process audits live code to produce a system manifest, navigable docs/index references, and tech stack mappings derived directly from production reality.

Does the code audit fill in missing product requirements with assumed features?

No, the code audit does not fill in missing product requirements with assumed features. It strictly converts existing production reality into documentation and avoids fabricating missing information during the PRD generation process.

Do I need any specific dependencies to extract documentation from my workspace?

You do not need any specific dependencies to extract documentation from your workspace. The process runs a deterministic workflow directly on your codebase to build the manifest and feature PRDs without requiring external components.