ralph

Manage tasks and preserve context across sessions with plan files and session logs.

2|3|Updated Jul 27, 2023
One-click install
npx skills add https://github.com/Freegle/FreegleDocker --skill ralph-freegle
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ralph
Source: https://github.com/Freegle/FreegleDocker/tree/main/.claude/skills/ralph
Command: npx skills add https://github.com/Freegle/FreegleDocker --skill ralph-freegle

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This metadata-driven approach provides a structured, auditable workflow for software tasks by enforcing plan-driven progress, session logging, and one-task-at-a-time execution to preserve context across sessions.

Core Features & Use Cases

  • Structured planning: A plan file and status tables drive task progression, ensuring repeatable workflows.
  • Context continuity: Session logs capture decisions, blockers, and outcomes to enable seamless resumption.
  • Quality gate: Built-in guidance for task validation, code quality reviews, and mandatory testing before closure.
  • Applicable scope: Ideal for feature work, bug fixes, refactoring, and any multi-step task in FreegleDocker.

Quick Start

Begin by updating CLAUDE.md with a new session entry and open the active plan file to start the first pending task.

Frequently Asked Questions about ralph

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

FAQPage Schema
How do I preserve development context across sessions for iterative tasks?

Session logging preserves development context across sessions by capturing decisions, blockers, and outcomes in structured logs. This enables seamless resumption of iterative tasks without losing prior progress or historical reasoning.

What is plan-driven iterative development and when do I need it?

Plan-driven iterative development uses a plan file and status tables to guide tasks one at a time from planning through validation. It is needed for multi-step feature work, bug fixes, and refactoring requiring auditable progress tracking.

Does plan-driven development require test-driven development for bug fixes and refactoring?

Plan-driven development requires test-driven development when applicable, followed by a mandatory code quality review before task completion. This ensures all bug fixes and refactoring tasks pass thorough validation and quality gates.

What's the best way to track task status in a structured development workflow?

The best way to track task status is using a plan file with status tables that drive task progression. This metadata-driven approach ensures repeatable workflows by enforcing one-task-at-a-time execution and mandatory status updates.

Can I use session logging for multi-step refactoring tasks in FreegleDocker?

Session logging is ideal for multi-step refactoring tasks in FreegleDocker. It captures decisions and outcomes across sessions, enabling seamless resumption while the plan file enforces structured progression through each refactoring step.