skills.rest
sequenzia
sequenziaCOMMUNITY
Explore all skills by this author →
Website𝕏@sequenziaGitHub

inverted-spec

Reverse-engineer codebases into provenance-annotated SDD pipeline specifications.

2|Updated Mar 9, 2026
Search Tags:#templates#documentation#provenance#code-analysis#spec-generation#requirements-engineering#inverted-spec
One-click install
npx skills add https://github.com/sequenzia/agent-tools --skill inverted-spec
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: inverted-spec
Source: https://github.com/sequenzia/agent-tools/tree/main/plugins/sdd/skills/inverted-spec
Command: npx skills add https://github.com/sequenzia/agent-tools --skill inverted-spec

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Inverted-spec analyzes an existing codebase to derive a comprehensive specification that can drive the SDD pipeline, transforming code structure and behavior into a documented, testable artifact.

Core Features & Use Cases

  • Interactive codebase analysis to extract architecture, flows, and constraints
  • Phase-guided interactive curation to validate findings and fill gaps via interviews
  • Output a complete inverted-spec document with provenance markers for traceability
  • Optional research stage to enrich findings with external best practices
  • Seamless mapping from analysis to spec templates across all depth levels

Quick Start

Specify the codebase path and start the inverted-spec workflow to generate the spec.

Frequently Asked Questions about inverted-spec

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

FAQPage Schema
How do I extract requirements and specifications from an existing codebase?▼

To extract specifications from an existing codebase, you can use a reverse-engineering process that analyzes code structure and behavior to generate a comprehensive, testable spec document. This approach transforms implemented logic into documented requirements with traceable provenance.

What is the best way to document hidden requirements in legacy code?▼

Documenting hidden requirements in legacy code works best through interactive curation and gap-filling interviews. This process validates extracted architecture and flows, surfacing implicit constraints to produce a structured, provenance-annotated specification with traceable decisions.

How do I generate a spec compatible with the SDD pipeline from source code?▼

Generating an SDD-compatible spec from source code involves analyzing the codebase to map architecture and constraints directly into spec templates. The output is a structured document designed to seamlessly drive the SDD pipeline across all depth levels.

Can I trace specific code structures back to their generated requirements?▼

Yes, tracing code structures to generated requirements is possible using provenance markers. The reverse-engineering process outputs a provenance-annotated document, ensuring every decision and derived requirement remains traceable to the original codebase.

Does reverse-engineering specifications work for complex codebases with missing documentation?▼

Reverse-engineering specifications effectively handles complex codebases with missing documentation by using phase-guided interactive curation. It analyzes existing flows to fill gaps via interviews, optionally enriching findings with external best practices.

Related Skills

Explore More Software Engineering Skills→
telum-aitelum-ai
2

project-import

Create a Speck project structure with a skeleton project.md file.

Official
Basic
keturkketurk
2

troubleshoot-and-fix

Diagnose and fix test failures in generated code pipelines.

Community
Advanced
johan--johan--

convert-to-speckit

Convert manual reverse engineering documentation into GitHub Spec Kit specifications.

Community
Intermediate
hypnguyen1209hypnguyen1209
338

reverse-engineering

Reverse-engineer binaries and firmware through static and dynamic analysis.

Community
Advanced