skills.rest
realsigridjin
realsigridjinCOMMUNITY
Explore all skills by this author →
Website𝕏@realsigridjinGitHub

ralph-init

Create a structured Product Requirements Document from a project description.

20|6|Updated Feb 13, 2026
Search Tags:#project planning#acceptance criteria#requirements gathering#prd#implementation phases#ralph loop
One-click install
npx skills add https://github.com/realsigridjin/oh-my-codex --skill ralph-init-realsigridjin
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ralph-init
Source: https://github.com/realsigridjin/oh-my-codex/tree/main/skills/ralph-init
Command: npx skills add https://github.com/realsigridjin/oh-my-codex --skill ralph-init-realsigridjin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill transforms a project or feature idea into a structured Product Requirements Document, reducing ambiguity and giving iterative implementation a clear definition of done.

Core Features & Use Cases

  • Requirements Gathering: Collects requirements through an interactive interview or an initial project description.
  • Structured PRD Creation: Defines the problem, goals, non-goals, acceptance criteria, constraints, and implementation phases.
  • Ralph Integration: Links the PRD to Ralph so iterative execution can continue until the documented acceptance criteria are met.
  • Use Case: Use it to turn a loosely defined feature request into a testable implementation plan for a multi-step engineering project.

Quick Start

Ask the ralph-init skill to create a PRD for your project or feature idea.

Frequently Asked Questions about ralph-init

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

FAQPage Schema
How do I create a PRD from a feature idea with testable acceptance criteria?▼

To create a PRD from a feature idea, you can provide an initial project description or go through an interactive interview to gather requirements, which then generates a structured document with testable acceptance criteria and phased execution plans.

What is the best way to define non-goals and implementation phases for software projects?▼

Defining non-goals and implementation phases for software projects is achieved by generating a structured Product Requirements Document that explicitly separates goals from non-goals and breaks down the work into distinct execution phases.

Can I use an initial project description to generate a complete product requirements document?▼

Yes, you can use an initial project description to generate a complete product requirements document, or you can choose to define your requirements through an interactive interview process.

How does a PRD link to iterative implementation processes for engineering projects?▼

A PRD links to iterative implementation by connecting the documented acceptance criteria to Ralph, serving as the completion criteria so iterative execution continues until all specified requirements are fully met.

Do I need a loosely defined feature request to start requirements gathering for a PRD?▼

You do not need a fully defined request to start requirements gathering; the process is designed to take a loosely defined feature request and transform it into a clear, testable implementation plan for multi-step engineering projects.

Related Skills

Explore More Product & Management Skills→
jtsang4jtsang4
2

plan-me

Guide users through structured interviews to create comprehensive project plans.

Community
Intermediate
Yeachan-HeoYeachan-Heo
32.6k

ralph-init

Generate a PRD with goals, constraints, and implementation phases from a project description.

Community
Intermediate
TienchingTienching
3

ralph-init

Generate a canonical PRD and initialize Ralph progress tracking.

Community
Intermediate
patcarter883patcarter883

gsdd-new-milestone

Collect goals, define requirements, and outline phases for the next development milestone.

Community
Basic