super-ralph-reverse

Stamp reverse process beads to generate a clean-room specification.

3|Updated Feb 21, 2026
One-click install
npx skills add https://github.com/mwarger/super-ralph --skill super-ralph-reverse
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: super-ralph-reverse
Source: https://github.com/mwarger/super-ralph/tree/main/skills/super-ralph-reverse
Command: npx skills add https://github.com/mwarger/super-ralph --skill super-ralph-reverse

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill helps teams convert ambiguous inputs into a precise, shareable clean-room specification by stamping a structured epic and a fixed sequence of beads (deep study, draft spec, fresh-eyes reviews, and consolidation).

Core Features & Use Cases

  • Bead-stamping workflow: classify input types, seed an epic, and generate a complete bead graph with dependencies.
  • Comprehensive guidance for clean-room specification: from analysis to verification, with explicit interfaces, data models, and constraints.
  • Use Case: A developer provides a description or repo URL and receives a fully defined spec workflow ready for execution in a Ralph loop.

Quick Start

Describe your input in natural language and I will stamp an epic and six beads to capture a clean-room specification.

Frequently Asked Questions about super-ralph-reverse

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

FAQPage Schema
How do I generate a clean-room specification from existing source code?

A clean-room specification workflow applies reverse engineering by stamping six sequential beads: deep study, draft spec, three fresh-eyes review passes, and consolidation. This structured process transforms ambiguous inputs into a precise specification with explicit interfaces and data models.

What is the best way to structure a clean-room specification workflow for verification?

The best way to structure a clean-room specification workflow is by stamping a fixed sequence of six beads. This sequence covers deep study, draft spec, fresh-eyes reviews, and consolidation, ensuring comprehensive guidance from initial analysis through final verification.

How do I wire dependencies in a bead graph for a clean-room spec?

To wire dependencies in a bead graph for a clean-room spec, the workflow automatically stamps the six beads and connects them. It seeds an epic from your input and maps the dependencies across deep study, drafting, fresh-eyes passes, and consolidation.

What inputs are needed to start the bead-stamping workflow for software engineering?

To start the bead-stamping workflow for software engineering, you need to provide an input such as a local source code path, a GitHub repository URL, or a natural language textual description of your project. This input is classified to seed the epic.

When should I use reverse process bead stamping instead of writing a specification manually?

You should use reverse process bead stamping when you need to convert ambiguous inputs into a precise, shareable clean-room specification. It automates dependency wiring and epic reporting, ensuring comprehensive coverage through fresh-eyes review passes.