ralph-it

Analyze GitHub PRDs to recommend the next user story with a concrete plan.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the end-to-end workflow for turning PRD GitHub issues into actionable development work by analyzing PRD content, mapping to merged PRs, and recommending the next user story with a concrete plan.

Core Features & Use Cases

  • PRD parsing and context extraction: Reads a PRD from a GitHub issue and extracts user stories and expectations.
  • Contextual analysis of past work: Scans merged PRs to identify completed stories and relevant findings.
  • Next-story planning and implementation plan: Proposes the next user story with dependencies, plan steps, and success criteria.
  • PRD-linked PR creation: Generates a PR and links it back to the original PRD issue, documenting findings for follow-up.

Quick Start

Provide a PRD GitHub issue URL or number to begin, and let this skill fetch, analyze, plan, and outline the next actionable steps.

Frequently Asked Questions about ralph-it

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

FAQPage Schema
How do I automate turning a GitHub PRD issue into an actionable user story?

To automate PRD-driven story planning, provide a GitHub PRD issue URL or number. The Skill fetches the PRD, parses user stories, scans merged PRs for context, and recommends the next story with a concrete implementation plan.

How does PRD analysis map completed work to merged pull requests?

PRD analysis maps completed work by scanning merged PRs to identify finished stories and relevant findings. It baselines work against these merged PRs and PRD references, determining dependencies, completed items, and gaps to recommend the next work item.

Can I trace implemented user stories back to the original PRD issue?

Yes, you can trace implemented work back to the PRD issue. The Skill generates a PR linked directly to the original PRD issue, documenting findings and dependencies for future work, ensuring full traceability throughout the development lifecycle.

What do I need to start planning the next user story from a PRD?

To start planning the next user story from a PRD, you need a GitHub PRD issue URL or number. The Skill automatically fetches the issue content, analyzes past PRs, and outlines the next actionable development steps with no additional dependencies required.

What is the best way to identify gaps and dependencies in a GitHub PRD?

The best way to identify PRD gaps and dependencies is by scanning the PRD issue against merged PRs. The Skill determines completed stories, finds missing work items, and recommends the next user story with dependencies, plan steps, and success criteria.