convert-to-speckit

Convert manual reverse engineering documentation into GitHub Spec Kit specifications.

1|Updated Jan 24, 2026

Search Tags:#test automation #code conversion #reverse engineering #specification creation #GitHub Spec Kit

Ready to run

npx skills add https://github.com/johan--/stackshift --skill convert-to-speckit-johan

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: convert-to-speckit
Source: https://github.com/johan--/stackshift/tree/main/skills/convert-to-speckit
Command: npx skills add https://github.com/johan--/stackshift --skill convert-to-speckit-johan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires markdown, github, and includes scripts (resource) and references (resource) components.

What problem does it solve?

Converts manual reverse engineering documentation into GitHub Spec Kit specifications, streamlining the process of implementing automated tests.

Core Features & Use Cases

Documentation Conversion: Automates the transformation of documentation into a Spec Kit format, facilitating continuous testing.
Spec Kit Ready: Outputs specifications compatible with GitHub's Spec Kit, ready for the /speckit-* workflow commands.
Use Case: For developers seeking to convert their reverse engineering documentation into a Spec Kit format for enhanced automated testing practices.

Quick Start

Run the convert-to-speckit skill on the repository with your documentation files present to create spec files in the GitHub Spec Kit format.

Frequently Asked Questions about convert-to-speckit

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

FAQPage Schema

How do I convert reverse engineering documentation into GitHub Spec Kit specifications?▼

To convert reverse engineering documentation into GitHub Spec Kit specifications, run the skill on a repository containing structured markdown inputs to generate spec files compatible with Spec Kit workflows. This streamlines implementing automated tests.

What is the best way to automate test specification creation from existing codebase documentation?▼

Automating test specification creation from existing codebase documentation is best handled by transforming structured markdown inputs into a Spec Kit format. This outputs specifications ready for GitHub's continuous testing workflows, bypassing manual specification creation.

Do I need structured markdown files to generate Spec Kit specifications for automated testing?▼

Yes, you need structured markdown files. The skill operates within the constraints of Spec Kit and requires structured markdown inputs for accurate feature detection and template-driven output generation.

Can I use GitHub Spec Kit workflow commands directly after converting my codebase documentation?▼

Yes, you can use GitHub Spec Kit workflow commands directly after conversion. The skill outputs Spec Kit ready specifications that are immediately compatible with the `/speckit-*` workflow commands for test automation.

Why does codebase documentation conversion require templates for output generation?▼

Codebase documentation conversion requires templates because the skill operates within the constraints of Spec Kit, relying on these templates to accurately format the structured markdown inputs into valid specification files.