How does the skill handle logic it isn't sure about?

The skill uses a Unified Tag System (like [Inferred] or [Unknown]) to flag logic that isn't explicitly defined, prompting the user to provide the necessary business context.

Does it support automated test analysis?

Yes, it scans existing test files to identify boundary conditions and behaviors, converting them into documented acceptance criteria.

Is this skill compatible with BDD and TDD workflows?

Absolutely. It integrates with /bdd and /tdd commands to convert extracted requirements into Gherkin scenarios and identify test coverage gaps.

Can I use this for refactoring projects?

Yes, it is specifically designed to create a 'source of truth' specification of current behavior, which serves as a baseline before beginning migrations or refactors.

Reverse Engineering to SDD

Name: Reverse Engineering to SDD
Author: ValorVie

byValorVie

•

Learning & Documentation

Converts legacy or undocumented code into structured SDD specification documents with strict anti-hallucination standards.

This skill automates the process of extracting technical specifications from existing codebases, transforming undocumented or legacy implementations into clear Spec-Driven Development (SDD) documentation. It systematically analyzes API endpoints, data models, and test cases while enforcing high-certainty labeling to distinguish between code-verified facts and inferred logic. By requiring human input for business context and motivations, it ensures that your system documentation remains an accurate, high-fidelity reflection of the actual implementation, making it an essential tool for system audits, onboarding, and large-scale refactoring projects.

Key Features

01Mandatory source attribution linking every specification point directly to specific lines of code.

02Strict anti-hallucination labeling using [Confirmed], [Inferred], and [Unknown] tags for maximum accuracy.

03Integrated pipeline support for BDD Gherkin scenario generation and TDD gap analysis.

04Test-to-requirement mapping that transforms existing test suites into formal acceptance criteria.

05Automated extraction of API routes, data models, and function signatures from source code.

063 GitHub stars

Use Cases

01Documenting legacy systems that lack original technical specifications or design documents.

02Accelerating developer onboarding by providing structured, source-linked summaries of existing module behaviors.

03Performing code archaeology to understand complex business logic before starting a major refactor.

Key Features

01Mandatory source attribution linking every specification point directly to specific lines of code.

02Strict anti-hallucination labeling using [Confirmed], [Inferred], and [Unknown] tags for maximum accuracy.

03Integrated pipeline support for BDD Gherkin scenario generation and TDD gap analysis.

04Test-to-requirement mapping that transforms existing test suites into formal acceptance criteria.

05Automated extraction of API routes, data models, and function signatures from source code.

063 GitHub stars

Use Cases

01Documenting legacy systems that lack original technical specifications or design documents.

02Accelerating developer onboarding by providing structured, source-linked summaries of existing module behaviors.

03Performing code archaeology to understand complex business logic before starting a major refactor.