skills.rest
Pyl-Tech
Pyl-TechOFFICIAL
Explore all skills by this author →
WebsiteGitHub

reverse-spec

Generate Stream Coding-compatible AS-IS module specs from existing codebases.

Updated Aug 23, 2026
Search Tags:#specification#verification#legacy code#documentation-first#reverse-engineering#API schemas#migration readiness
One-click install
npx skills add https://github.com/Pyl-Tech/stream-coding --skill reverse-spec-pyl-tech
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: reverse-spec
Source: https://github.com/Pyl-Tech/stream-coding/tree/main/.agents/skills/reverse-spec
Command: npx skills add https://github.com/Pyl-Tech/stream-coding --skill reverse-spec-pyl-tech

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns an undocumented or legacy codebase into precise Stream Coding-compatible specifications so AI development can be verified against reality instead of guesswork.

Core Features & Use Cases

  • Complete codebase inventory: reads every source file (not just entry points) and reports a files-read coverage ratio to ensure you didn’t skim.
  • One spec per module (AS-IS): produces module specs that capture exact interfaces, endpoints, schemas, events, database fields, validation rules, and error propagation as implemented today.
  • Spec validation and conformity gates: runs structural prechecks and conformance checks against the code, then generates a REVERSE-SPEC report with gaps, assumptions, and tech debt.

Quick Start

Use the reverse-spec skill to onboard a legacy project into Stream Coding by generating AS-IS module specs, validating them against the code, and producing a readiness report.

Frequently Asked Questions about reverse-spec

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

FAQPage Schema
How do I generate API schemas and specifications from legacy code?▼

Reverse-engineering specifications from legacy code involves recursively reading every source file to document exact interfaces, endpoints, schemas, and events module-by-module, eliminating undocumented-behavior drift.

What is the best way to document legacy code before a migration?▼

The best way to document legacy code for migration readiness is generating one AS-IS spec per module that captures exact validation rules, database fields, and error propagation, followed by structural prechecks and conformance validation to produce a readiness report.

Can I reverse-engineer specifications without reading every source file?▼

No, reverse-engineering specifications requires full recursive source-file reading with a 100% coverage check. This ensures the generated AS-IS module specs accurately capture the codebase's exact signatures and schemas instead of skimming entry points.

How do I check if my existing code conforms to newly generated specifications?▼

To check spec-code conformance, run structural prechecks and conformance checks against the codebase after generating AS-IS module specs. This produces a REVERSE-SPEC report highlighting gaps, assumptions, and tech debt.

When do I need to reverse-engineer specifications from an existing codebase?▼

You need to reverse-engineer specifications from an existing codebase during legacy onboarding, migrations, or when adopting Stream Coding without prior specs, serving as a prerequisite before running strategy or hardening workflows.

Related Skills

Explore More Software Engineering Skills→
micaelmaltamicaelmalta
1

rlm

Coordinate sub-agents to analyze large codebases without overflowing context.

Community
Advanced
liqiongyuliqiongyu
51

managing-tech-debt

Generate a Tech Debt Management Pack with debt register, scoring, and strategy decisions.

Community
Advanced
rhussrhuss
107

implement

Generate implementation plans and TDD cycles from validated specifications.

Community
Basic
ricardops34ricardops34

reversa-writer

Generate executable specification artifacts from reverse-engineered legacy knowledge.

Community
Advanced