skills.rest
jschulte
jschulteCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

create-specs

Generate formal feature specifications and plans from reverse-engineering documentation using Speckit.

3|3|Updated Nov 16, 2025
One-click install
npx skills add https://github.com/jschulte/claude-plugins --skill create-specs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: create-specs
Source: https://github.com/jschulte/claude-plugins/tree/main/stackshift/skills/create-specs
Command: npx skills add https://github.com/jschulte/claude-plugins --skill create-specs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires specify-cli, and includes references (resource) components.

What problem does it solves? Transforming raw documentation into structured, actionable specifications can be a manual and error-prone process. This skill automates the integration with GitHub Spec Kit, converting your reverse-engineered documentation into formal, machine-readable specifications ready for automated development.

Core Features & Use Cases

  • Spec Kit Initialization: Automatically set up the .specify/ directory structure for spec-driven development.
  • Constitution Generation: Create a constitution.md outlining project principles and standards from your functional specification.
  • Feature Specification: Generate individual feature specifications and initial implementation plans from your detailed documentation.
  • Use Case: After reverse-engineering a codebase, you have extensive documentation. Use this skill to automatically convert that into a structured specs/ directory, enabling you to use /speckit commands for validation, planning, and implementation, ensuring consistency between code and documentation.

Quick Start

Create specifications from the reverse-engineered documentation in docs/reverse-engineering/.

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-engineered documentation into structured specifications?▼

Convert reverse-engineered documentation into structured specifications by using this Skill to automatically parse your functional specification, generate a constitution.md file, and create individual feature specs in the .specify/ directory. The Skill reads docs/reverse-engineering/functional-specification.md and outputs machine-readable specs ready for spec-driven development workflows.

What does a constitution.md file do in spec-driven projects?▼

Constitution.md outlines your project's principles, standards, and architectural guidelines extracted from your functional specification. It serves as the foundational document for all downstream feature specifications and ensures consistency across your codebase and documentation.

Can I generate implementation plans and tasks from my documentation?▼

Yes. Beyond basic specifications, this Skill supports three thoroughness modes: specs-only, specs with plans, and specs with plans and tasks. For partial or missing features, it generates plan.md and tasks.md files to guide implementation alongside your formal specifications.

Do I need reverse-engineering documentation before using this Skill?▼

Yes. This Skill requires comprehensive reverse-engineering documentation in docs/reverse-engineering/functional-specification.md. It parses and extracts features from existing documentation rather than generating documentation from code.

How does this integrate with GitHub Spec Kit?▼

Once initialized, the .specify/ directory structure enables /speckit slash commands for validation, planning, and implementation. The Skill configures execution from .stackshift-state.json and ensures your documentation-derived specs work seamlessly with spec-driven development tooling.

What happens to features that are only partially documented?▼

Partial and missing features receive individual spec files in .specify/specs/ with optional accompanying plan.md and tasks.md files depending on your selected thoroughness mode, enabling you to track and plan implementation for gaps in your documentation.

Related Skills

jschultejschulte
3

create-specs

Generate formal feature specifications and plans from reverse-engineering documentation using Speckit.

Community
Intermediate
jschultejschulte
3

implement

Automates implementing missing features from finalized specifications via Speckit workflows.

Community
Intermediate
sabrydawoodsabrydawood
1

speckit-constitution

Fill placeholder governance tokens into the Speckit constitution memory file.

Community
Advanced
johan--johan--

convert-to-speckit

Convert manual reverse engineering documentation into GitHub Spec Kit specifications.

Community
Intermediate