create-specs

Convert reverse-engineering documentation into GitHub Spec Kit format.

1|Updated Jan 24, 2026
One-click install
npx skills add https://github.com/johan--/stackshift --skill create-specs-johan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-specs
Source: https://github.com/johan--/stackshift/tree/main/skills/create-specs
Command: npx skills add https://github.com/johan--/stackshift --skill create-specs-johan

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the transformation of reverse-engineering documentation into GitHub Spec Kit format, streamlining the process of transitioning from reverse engineering to spec-driven development.

Core Features & Use Cases

  • Documentation Conversion: Converts reverse-engineering documentation into GitHub Spec Kit format.
  • Initialization of .specify/ Directory: Initializes the .specify/ directory and creates necessary files like constitution.md.
  • Feature Spec Generation: Generates feature specifications from reverse-engineered documents.
  • Slash Command Setup: Sets up /speckit slash commands for further development and implementation.
  • Use Case: Ideal for software development teams looking to adopt a spec-driven approach and integrate with GitHub Spec Kit.

Quick Start

Run the 'create-specs' skill to transform your reverse-engineering documentation into GitHub Spec Kit format.

Frequently Asked Questions about create-specs

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 format?

To convert reverse-engineering documentation into GitHub Spec Kit format, run the 'create-specs' skill. It automates transformation by initializing the .specify/ directory, creating constitution.md, generating feature specs, and setting up slash commands.

What files and directories does GitHub Spec Kit initialization need?

GitHub Spec Kit initialization requires a .specify/ directory containing a constitution.md file, feature specifications derived from your documentation, and slash command configurations to facilitate downstream spec-driven development.

Do I need automated spec generation tools to use create-specs?

Yes, you need the F002 automated spec generation tools. The create-specs skill requires this dependency to successfully automate documentation transformation and initialize the GitHub Spec Kit directory structure.

When should I use spec-driven development with reverse-engineered documentation?

Use spec-driven development with reverse-engineered documentation when transitioning from analysis to implementation. This approach converts existing system knowledge into structured feature specs, ensuring code aligns with documented behaviors.

Can I set up /speckit slash commands from existing reverse-engineered documents?

Yes, you can set up /speckit slash commands from existing reverse-engineered documents. The skill generates these commands during transformation into GitHub Spec Kit format to support further development and implementation.