starting-a-reverse-eng

Convert legacy source code into evidence-backed SDD_Pro FEATs.

140|20|Updated Jun 20, 2026
One-click install
npx skills add https://github.com/zekiriabd/SDD-Pro --skill starting-a-reverse-eng
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: starting-a-reverse-eng
Source: https://github.com/zekiriabd/SDD-Pro/tree/main/.sdd/skills/starting-a-reverse-eng
Command: npx skills add https://github.com/zekiriabd/SDD-Pro --skill starting-a-reverse-eng

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents ad hoc audits and unsafe rewrites by guiding the structured reverse engineering of legacy source code into evidence-backed SDD_Pro FEATs.

Core Features & Use Cases

  • Strict Triggering: Activates only for explicit reverse-engineering and legacy-migration requests, avoiding interception of ordinary refactoring tasks.
  • Phased Workflow: Coordinates source verification, project initialization, inventory generation, unit-level FEAT extraction, human review, validation, and handoff to the standard SDD pipeline.
  • Quality Guardrails: Requires evidence and confidence annotations, applies conservative documentation rules, supports multiple legacy languages, and blocks unsupported binary-only inputs.
  • Use Case: Use this Skill to map an existing ASPX, Java, PHP, Delphi, or other legacy application into functional units and produce reviewable FEATs for staged reimplementation.

Quick Start

Ask the AI to reverse engineer the legacy project located in workspace/old/LegacyProject and convert its functional units into validated SDD_Pro FEATs.

Frequently Asked Questions about starting-a-reverse-eng

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

FAQPage Schema
How do I reverse engineer legacy code into structured functional units?

Reverse engineering legacy code into structured units requires verifying source files, generating a codebase inventory, and extracting unit-level FEATs with strict evidence and confidence annotations for human review.

What is the best way to migrate legacy ASPX or Delphi applications safely?

The best way to migrate legacy ASPX or Delphi applications is a phased workflow that extracts evidence-backed functional units, applies confidence annotations, and requires human review gates before reimplementation.

Can I extract FEATs from legacy PHP and Java codebases?

Yes, you can extract FEATs from legacy PHP and Java codebases by placing source files in the workspace and running phased inventory and unit-level extraction to produce reviewable functional specifications.

How do I prevent unsafe ad hoc rewrites during software modernization?

Preventing unsafe ad hoc rewrites during software modernization requires structured reverse engineering with source verification, conservative documentation rules, and validation gates before entering the standard pipeline.

Does this reverse engineering workflow support binary-only legacy inputs?

No, this reverse engineering workflow does not support binary-only legacy inputs; it requires accessible source code for ASPX, Java, PHP, Delphi, or other supported languages to generate evidence-backed FEATs.