ralph-plan

Converts verbose design documents into Ralph-compatible markdown checkbox plan files.

Updated Apr 1, 2021
One-click install
npx skills add https://github.com/danielukea/.dotfiles --skill ralph-plan-danielukea
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ralph-plan
Source: https://github.com/danielukea/.dotfiles/tree/main/claude/.claude/skills/ralph-plan
Command: npx skills add https://github.com/danielukea/.dotfiles --skill ralph-plan-danielukea

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the process of turning detailed design documents or verbose plans into concise, actionable steps that the Ralph AI can execute.

Core Features & Use Cases

  • Design to Actionable Steps: Converts lengthy design documents into a flat list of markdown checkboxes for AI execution.
  • Contextualization: Gathers necessary environment context (credentials, commands, conventions) for the AI.
  • Use Case: You have a detailed feature design document. Use this Skill to transform it into a series of clear, executable tasks for an AI developer to implement.

Quick Start

Use the ralph-plan skill to convert the design document located at './local/feature-design.md' into a ralph-compatible plan.

Frequently Asked Questions about ralph-plan

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

FAQPage Schema
How do I convert a design document into actionable steps for AI development?

This skill converts verbose design documents into concise, Ralph-compatible markdown plan files with checkbox steps. It reads your source document, gathers necessary environment context via questions, and formats the output into structured, executable tasks.

What is the best way to format unstructured design text into a markdown task list?

The best way is to transform unstructured design text into a flat list of markdown checkboxes formatted for AI execution. This ensures the output meets specific AI execution formatting requirements while capturing all necessary steps.

Do I need to provide environment context when generating a plan from a design document?

Yes, you need to provide environment context when generating a plan. The process actively gathers necessary context such as credentials, commands, and conventions to ensure the AI developer has the information required to execute the structured tasks.

Can I automate the transformation of lengthy feature design documents into AI plans?

Yes, you can automate the transformation of lengthy feature design documents into AI plans. The skill reads the source design file and automatically converts the verbose text into structured, executable tasks without manual formatting.

Are there limitations when converting verbose plans into markdown checkboxes?

A limitation is that the output is a flat list of checkbox steps, which may lose nuanced details from the original verbose document. Additionally, the process requires user interaction to gather necessary environment context before generating the final plan.