ralph-spec

Define machine-actionable Ralph specs with INVESTIGATE, BUILD, VERIFY, and DECOMPOSE stages.

Updated Jul 28, 2023
One-click install
npx skills add https://github.com/djmittens/neo-mittens --skill ralph-spec
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ralph-spec
Source: https://github.com/djmittens/neo-mittens/tree/main/.opencode/skills/ralph-spec
Command: npx skills add https://github.com/djmittens/neo-mittens --skill ralph-spec

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ralph specs enable autonomous task execution by translating requirements into machine-actionable instructions that Construct mode can execute end-to-end.

This guide ensures specs are unambiguous, verifiable, and decomposable into INVESTIGATE, BUILD, VERIFY, and DECOMPOSE stages, reducing handoff delays and rework.

Core Features & Use Cases

  • Structured specification templates with mandatory sections (Overview, Requirements, Acceptance Criteria) to enable repeatable, verifiable builds.
  • Guidance for edge cases, dependency management, and phased implementation to prevent task-level circular dependencies.
  • Clear artifacts outputs (spec files placed in ralph/specs) and validation criteria that map directly to automated tasks.

Quick Start

Place a new spec at ralph/specs/<spec-name>.md and run Ralph construct <spec-name> to begin autonomous implementation.

Frequently Asked Questions about ralph-spec

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

FAQPage Schema
How do I define machine-actionable requirements for autonomous task automation?

You define machine-actionable requirements by creating structured Ralph specs with mandatory Overview, Requirements, and Acceptance Criteria sections that Construct mode can autonomously implement end-to-end.

How do I structure acceptance criteria for automated build verification?

Acceptance criteria for automated build verification must be concrete and map directly to automated tasks, ensuring specs are verifiable and decomposable into INVESTIGATE, BUILD, VERIFY, and DECOMPOSE iterations.

What is the best way to prevent circular dependencies in phased implementation specs?

The best way to prevent circular dependencies is using Ralph specs that provide explicit guidance for edge cases, dependency management, and phased implementation to reduce handoff delays and rework.

How do I start autonomous implementation from a specification file?

To start autonomous implementation, place a new spec at ralph/specs/<spec-name>.md and run Ralph construct <spec-name> to trigger automated execution of the defined requirements.

When do I need to decompose requirements into INVESTIGATE, BUILD, VERIFY, and DECOMPOSE stages?

You need to decompose requirements into these stages when features require unambiguous requirements, verifiable acceptance criteria, and clearly scoped iterations for autonomous task execution.

Can I use Ralph specs for features requiring rigorous error handling guidance?

Yes, Ralph specs satisfy rigorous requirements and provide robust guidance for verification and error handling, ensuring autonomous execution handles edge cases without manual intervention.