🎯

ralph-github-create-issues

🎯Skill

from richtabor/agent-skills

VibeIndex|
What it does

Here's a concise, practical description for the "ralph-github-create-issues" skill: Converts PRD markdown files into structured GitHub Issues, enabling seamless product requirement tracking and im...

πŸ“¦

Part of

richtabor/agent-skills(14 items)

ralph-github-create-issues

Installation

Quick InstallInstall with npx
npx skills add richtabor/agent-skills
Add MarketplaceAdd marketplace to Claude Code
/plugin marketplace add https://github.com/richtabor/agent-skills
Install PluginInstall plugin from marketplace
/plugin install rt
πŸ“– Extracted from docs: richtabor/agent-skills
4Installs
-
AddedFeb 4, 2026

Skill Details

SKILL.md

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.

Overview

# 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

Branch

feature/

Quality Gates

```bash

npm run typecheck

npm run lint

npm test

```

Implementation Order

  1. Story one
  2. Story two

EOF

)"

```

Sub-Issues

For each story:

```bash

# Create issue

gh issue create \

--title "Story Title" \

--body "$(cat <<'EOF'

Files: path/to/file.tsx

Acceptance Criteria:

  • [ ] Specific change
  • [ ] Typecheck passes
  • [ ] Lint passes

Notes:

Context if needed.

EOF

)"

# Link to parent

gh sub-issue add

```

Dependencies

If dependencies detected in preflight, use GraphQL API (no extension needed):

```bash

# Get repo info

OWNER=$(gh repo view --json owner -q '.owner.login')

REPO=$(gh repo view --json name -q '.name')

# Get node IDs (replace 50 and 42 with actual issue numbers)

BLOCKED_ID=$(gh api graphql -f query="{ repository(owner: \"$OWNER\", name: \"$REPO\") { issue(number: 50) { id } } }" --jq '.data.repository.issue.id')

BLOCKING_ID=$(gh api graphql -f query="{ repository(owner: \"$OWNER\", name: \"$REPO\") { issue(number: 42) { id } } }" --jq '.data.repository.issue.id')

# Add blocked-by relationship

gh api graphql -f query="mutation { addBlockedBy(input: {issueId: \"$BLOCKED_ID\", blockingIssueId: \"$BLOCKING_ID\"}) { clientMutationId } }"

```

Output

```

Created: #50 - Feature Name

β†’ #51 Story One

β†’ #52 Story Two

Dependencies: Blocked by #42 (Auth Flow)

Branch: feature/

Run: /ralph-github-start-loop

```

Then ask:

```

Remove local plan/PRD file? (y/n)

```

If yes, delete the source file. GitHub Issue is now source of truth.

More from this repository10

πŸͺ
richtabor-agent-skillsπŸͺMarketplace

Provides Claude with specialized plugins for technical writing, accessibility reviews, motion design, and social media content creation across different platforms.

🎯
technical-writing🎯Skill

Generates technical blog posts by analyzing code implementations, crafting clear and engaging content that avoids AI-sounding language.

🎯
create-prd🎯Skill

Interactively plan and generate a comprehensive Product Requirements Document (PRD) by asking clarifying questions and structuring detailed feature specifications.

🎯
x-writing🎯Skill

Transforms notes and ideas into engaging X (Twitter) posts by analyzing content, applying strategic writing principles, and crafting authentic social media content.

🎯
fresh-eyes🎯Skill

Performs a detailed, critical re-read of recently modified code to catch bugs, errors, and potential issues from a fresh perspective.

🎯
humanize🎯Skill

Humanizes AI-generated text by removing robotic patterns, preserving meaning, and making writing sound more natural and authentic.

🎯
ralph-json-create-issues🎯Skill

Converts markdown PRD or plan files into structured JSON stories, ensuring right-sized, dependency-aware tasks for autonomous Ralph execution.

🎯
ralph-github-start-loop🎯Skill

Autonomously fetches, implements, and closes GitHub issues across multiple iterations, guiding development through PRD-labeled issues.

🎯
review-pr🎯Skill

Reviews GitHub PR comments, evaluates against current code, and automatically addresses reviewer feedback with precise reasoning.

🎯
og-images🎯Skill

Generates dynamic, customizable OpenGraph and Twitter share images for Next.js using ImageResponse with flexible layout and styling options.