ralph-spec-writer

Guide iterative stakeholder interviews to generate structured software specifications.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/jujumilk3/my-dotclaude --skill ralph-spec-writer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ralph-spec-writer
Source: https://github.com/jujumilk3/my-dotclaude/tree/main/skills/ralph-spec-writer
Command: npx skills add https://github.com/jujumilk3/my-dotclaude --skill ralph-spec-writer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill guides teams through deep, iterative interviews to generate comprehensive software specifications using the Ralph Wiggum methodology.

Core Features & Use Cases

  • Conduct multi-round interviews with stakeholders using AskUserQuestion to elicit requirements, constraints, and tradeoffs.
  • Produce structured specs (What, Why, Acceptance Criteria, Context) aligned with JTBDs and topics.
  • Capture edge cases, dependencies, decisions, and open questions to guide implementation planning.

Quick Start

  1. Initiate requirements gathering for a new feature and begin the iterative interview process.
  2. Break the scope into single-topic specs and draft corresponding documents.
  3. Export a complete spec set with decisions, tradeoffs, and acceptance criteria for the implementation plan.

Frequently Asked Questions about ralph-spec-writer

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

FAQPage Schema
How do I write software specifications using an iterative interview process?

To write software specifications through interviews, you guide stakeholders through deep, multi-round questioning to elicit requirements, constraints, and tradeoffs. This structured approach uses staged documentation to drive alignment and produce comprehensive specs.

What is the Ralph Wiggum methodology for spec writing?

The Ralph Wiggum methodology for spec writing is a disciplined, iterative interview process designed to generate comprehensive software specifications. It relies on structured questioning to capture edge cases, dependencies, and open questions for implementation planning.

How do I capture edge cases and dependencies when gathering requirements for system design?

Capturing edge cases and dependencies during requirements gathering requires breaking the project scope into single-topic specs. Through iterative interviews, you systematically extract and document these constraints alongside decisions and tradeoffs to guide implementation planning.

Can I use Jobs-to-be-Done (JTBD) analysis to structure my software requirements document?

Using JTBD analysis to structure software requirements involves aligning your specification documents with specific jobs-to-be-done and topics. This ensures the generated specs capture the exact requirements, acceptance criteria, and context needed for implementation.

What's the best way to document tradeoffs and open questions during feature spec writing?

Documenting tradeoffs and open questions during feature spec writing is best handled through a structured interview process that explicitly isolates single topics. This methodology captures decisions and open questions directly within the staged documentation for alignment.

Does automated spec writing work for complex system design with multiple stakeholders?

Automated spec writing works for complex system design by conducting multi-round interviews with multiple stakeholders. It systematically elicits requirements and constraints, exporting a complete spec set with structured acceptance criteria for the implementation plan.