Converts a PRD markdown file into GitHub Issues (parent + sub-issues) for ralph-github-start-loop to execute. Use when user wants to push PRD stories to GitHub Issues.
View on GitHubrichtabor/agent-skills
rt
February 1, 2026
Select agents to install to:
npx add-skill https://github.com/richtabor/agent-skills/blob/main/skills/ralph-github-create-issues/SKILL.md -a claude-code --skill ralph-github-create-issuesInstallation paths:
.claude/skills/ralph-github-create-issues/# Create PRD Issues
Convert a local PRD or plan file into GitHub Issues.
## Usage
```
/ralph-create-github-issues # Looks in .claude/plans/ then prds/
/ralph-create-github-issues auth-flow # Convert specific PRD by name
```
For story sizing and acceptance criteria guidance, see `references/best-practices.md`.
## Preflight
Run these checks. Stop if critical ones fail.
```bash
# 1. Auth check
gh auth status
# 2. Find plan/PRD files — check all locations
ls .claude/plans/*.md 2>/dev/null
ls plans/*.md 2>/dev/null
ls prds/*.md 2>/dev/null
# 3. PRD not already an issue (stop if found open)
gh issue list --label prd --state all --json number,title,state
# 4. Ensure prd label exists
gh label create prd --description "Product Requirements Document" --color "0052CC" 2>/dev/null || true
# 5. Get existing PRDs for dependency matching
gh issue list --label prd --state open --json number,title
```
### Where to find plans
Check these locations in order:
1. **`.claude/plans/`** — Where plan mode saves approved plans. This is the primary source.
2. **`plans/`** — Project-level plans directory.
3. **`prds/`** — Standalone PRDs not generated from plan mode.
If files exist in multiple locations, list all and ask which to convert. If only one file is found, use it directly. **If no files are found in any location, ask the user for the path to their PRD/plan file.**
Scan PRD markdown for dependency references ("depends on X", "see `feature.md`"). Note matches for later.
**Note:** Assume `gh sub-issue` and `gh issue-dependency` are already installed. Do NOT try to install them. Just run the commands — if they fail, skip that step and continue.
## Create Issues
### Parent Issue
```bash
gh issue create \
--title "Feature Name" \
--label "prd" \
--label "enhancement" \
--body "$(cat <<'EOF'
## Overview
<From PRD intro>
## Branch
`feature/<name>`
## Quality Gates
```bash
npm run typecheck
npm run lint
npm test
```
## Implementation Order
1. Stor