ralph

Generate dependency-ordered user stories and enforce quality gates during autonomous feature builds.

5|Updated Mar 27, 2026
One-click install
npx skills add https://github.com/barkleesanders/claude-code-starter --skill ralph-barkleesanders
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ralph
Source: https://github.com/barkleesanders/claude-code-starter/tree/main/skills/ralph
Command: npx skills add https://github.com/barkleesanders/claude-code-starter --skill ralph-barkleesanders

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the need for a separate standalone feature implementation workflow by consolidating all original Ralph functionality into the /carmack command, so you don't have to manage separate tools for autonomous feature development.

Core Features & Use Cases

  • Autonomous Feature Implementation Loop: /carmack handles end-to-end feature builds without manual step-by-step oversight.
  • Structured PRD & Story Management: Automatically generates a prd.json with user stories, orders them by dependency, and respects context window limits for each story.
  • Progress & Quality Tracking: Maintains an append-only progress.txt log and enforces language-specific quality gates for TypeScript, Rust, and Python.
  • Use Case: If you need to implement a new user profile editing feature, you can invoke /carmack to automatically plan the work, build each component in the correct order, track progress, and run all required quality checks before completion.

Quick Start

Use the /carmack command to autonomously implement your requested feature end-to-end.

Frequently Asked Questions about ralph

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

FAQPage Schema
How do I autonomously implement new features end-to-end without manual workflow steps?

Autonomous feature implementation is handled by the /carmack command, which generates a structured PRD, orders user stories by dependency, and executes builds sequentially to eliminate manual workflow orchestration across planning, coding, and quality checks.

What is structured PRD generation and how does it manage user stories for feature development?

Structured PRD generation creates a prd.json file containing user stories ordered by their dependencies. It automatically sizes stories to respect context window limits, ensuring each component is built in the correct sequence for autonomous feature builds.

How do I track progress and enforce quality gates for TypeScript, Rust, and Python builds?

Progress tracking uses an append-only progress.txt log to record build milestones, while language-specific quality gates are automatically enforced for TypeScript, Rust, and Python during the autonomous feature implementation loop to ensure code standards.

Does autonomous feature development work with multi-language quality gates and dependency-ordered execution?

Yes, autonomous feature development supports dependency-ordered execution and enforces multi-language quality gates for TypeScript, Rust, and Python. It contextually sizes user stories and maintains append-only progress logging throughout the build process.

What's the best way to plan and build a feature without managing separate development tools?

The best way is using a consolidated command that merges PRD generation, story breakdown, and quality enforcement into a single tool. This removes the need to manage separate standalone applications for autonomous feature implementation and progress tracking.

Why do I need to generate a prd.json file before breaking down user stories for autonomous builds?

Generating a prd.json file is required to structure user stories and order them by dependency before execution. This contextual story sizing ensures the autonomous build loop respects context window limits and implements features in the correct sequence.