skills.rest
abagames
abagamesCOMMUNITY
Explore all skills by this author →
Website𝕏@abagamesGitHub

extracting-spec-design-ladders

Extract source code into a reproduction spec and abstract design doc.

11|2|Updated May 7, 2026
Search Tags:#specification#source code#reverse engineering#design doc#artifact ladder
One-click install
npx skills add https://github.com/abagames/agentic-gamedev-skills --skill extracting-spec-design-ladders
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: extracting-spec-design-ladders
Source: https://github.com/abagames/agentic-gamedev-skills/tree/main/.agents/skills/extracting-spec-design-ladders
Command: npx skills add https://github.com/abagames/agentic-gamedev-skills --skill extracting-spec-design-ladders

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill helps you reverse-engineer existing source code into two distinct artifacts: a reproduction spec and an abstract design doc, which separates implementation details from design intent.

Core Features & Use Cases

  • Reverse Engineering: Transform source code into two-layer artifacts for clear documentation and recovery of program intent.
  • Separation of Concerns: Maintain a reproduction spec for rebuildable behavior and a design doc for understanding design intent without implementation details.
  • Use Case: Ideal for documenting or recovering a program's behavior without revealing implementation specifics, such as when creating technical documentation for a codebase.

Quick Start

Extract specifications and design from 'example-source-code.cpp' using the extracting-spec-design-ladders skill.

Frequently Asked Questions about extracting-spec-design-ladders

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

FAQPage Schema
How do I reverse engineer source code to extract design intent separate from implementation details?▼

This approach extracts source code into a two-layer artifact ladder, separating a reproduction spec for rebuildable behavior from an abstract design doc for understanding design intent without implementation details.

What is an artifact ladder and when do I need it for codebase documentation?▼

An artifact ladder is a two-layer documentation structure separating a reproduction spec from an abstract design doc. You need it when reverse engineering a codebase to recover program behavior and intent without exposing implementation specifics.

How do I create a reproduction spec from existing source code?▼

You create a reproduction spec by extracting source code into an artifact ladder. This process requires the source code, engine or convention docs, and validation against a preservation checklist to accurately document rebuildable behavior.

Do I need engine documentation or convention guides to extract a design doc from source code?▼

Yes, extracting a design doc requires engine or convention documentation alongside the source code. These references provide the necessary context to accurately separate abstract design intent from implementation details during the artifact ladder extraction.

What's the best way to document a program's behavior without revealing implementation specifics?▼

The best way is to use a two-layer artifact ladder that separates a reproduction spec from an abstract design doc. This method documents or recovers program behavior while keeping the underlying source code implementation details hidden.

How do I validate extracted specifications against a preservation checklist?▼

You validate extracted specifications by checking the generated reproduction spec and design doc against a preservation checklist. This ensures the artifact ladder accurately captures rebuildable behavior and abstract design intent from the source code.

Related Skills

Explore More Software Engineering Skills→
ActiveMemoryActiveMemory
74

consolidate

Consolidate the ctx codebase to fix code-level drift and enforce project conventions.

Official
Advanced
dsteven12dsteven12
1

doc-css-framework

Generate branded, print-ready Airtable documentation with CSS variables and component classes.

Community
Intermediate
AlbertLin821AlbertLin821
2

gitnexus-impact-analysis

Analyze git-staged changes to map upstream dependencies and affected execution flows.

Community
Advanced
chad3814chad3814

Code Documentation Style

Adds evergreen, explanatory comments to complex Rust code and workflows.

Community
Basic