ralph-it

Select and implement the next user story from a GitHub PRD issue.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pick and implement the next user story from a PRD GitHub issue. Analyzes merged PRs for prior work and findings, proposes a plan, implements it, and creates a PR linking back to the PRD. Use when user says "ralph it", "ralph-it", or wants to work through PRD user stories.

Core Features & Use Cases

  • Gather context from a PRD issue and historical PRs to identify unimplemented user stories.
  • Analyze merged PRs for prior work, findings, and dependencies to determine the next logical story.
  • Plan, implement, and create a PR that references the PRD, ensuring traceability back to the PRD.
  • Provide a structured handoff and loop for re-entry after PR creation.

Quick Start

Provide a GitHub PRD issue URL and I will select the next user story, plan the work, implement it, and create a PR linking back to the PRD.

Frequently Asked Questions about ralph-it

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

FAQPage Schema
How do I automate user story implementation from a GitHub PRD issue?

Automating user story implementation from a GitHub PRD issue involves selecting the next unimplemented story, planning the work, writing the code, and creating a PR. This Skill analyzes merged PRs for prior work and proposes a plan linking back to the PRD.

What is PRD-driven story planning in GitHub?

PRD-driven story planning in GitHub is the process of tracking product requirements by linking pull requests directly to a PRD issue. It analyzes merged PRs to determine the next logical story and ensures traceability between implementation and the PRD.

How do I track PRD progress using merged pull requests?

Tracking PRD progress using merged pull requests involves analyzing the PRs for prior findings and dependencies. This Skill automatically determines completed stories and selects the next unimplemented user story based on that merged PR history.

Can I link a new pull request back to a PRD issue automatically?

Yes, you can link a new pull request back to a PRD issue automatically. When implementation is complete, this Skill creates a PR that explicitly references the PRD, ensuring full traceability between the code changes and the product requirements.

Does this workflow require a specific format for PRD user stories?

This workflow requires a PRD GitHub issue that lists user stories. It uses the issue to gather context and identify unimplemented stories, so the PRD must exist as a GitHub issue containing the user stories you want to implement.

What is the best way to manage product development workflows with GitHub issues?

The best way to manage product development workflows with GitHub issues is to automate the loop between planning and implementation. This Skill selects the next user story from a PRD issue, implements it, and creates a PR with a structured handoff for re-entry.