ralph-convert-prd

ralph-convert-prd is a skill for Claude Code, Codex from cfircoo/claude-code-toolkit. It costs 57 tokens per session (2,920 once invoked), scanned B, original, MIT.

A converter that turns a Product Requirements Document—a written description of what a product should do—into prd.json tasks for the Ralph autonomous agent system.

In plain words
What is it for?
Preparing Ralph work by creating atomic user stories, verification commands, dependency links, and an execution order.
Why use it?
It breaks broad requirements into small, ordered stories with checks and dependencies that an automated agent can complete one at a time.

Skill for Claude CodeCodex

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/cfircoo/claude-code-toolkit/ralph-convert-prd
Any agent
npx skills add cfircoo/claude-code-toolkit --skill ralph-convert-prd
Clone the repo
git clone --depth 1 https://github.com/cfircoo/claude-code-toolkit

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for ralph-convert-prd

README.md
[![agentmods](https://agentmods.dev/badge/skills/cfircoo/claude-code-toolkit/ralph-convert-prd.svg)](https://agentmods.dev/skills/cfircoo/claude-code-toolkit/ralph-convert-prd)
Your own site
<a href="https://agentmods.dev/skills/cfircoo/claude-code-toolkit/ralph-convert-prd"><img src="https://agentmods.dev/badge/skills/cfircoo/claude-code-toolkit/ralph-convert-prd.svg" alt="Measured on agentmods" height="20"></a>
Per session 57 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,920 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 2 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00057 $0.02920
Opus 5 $0.00028 $0.01460
Sonnet 5 $0.00011 $0.00584
Haiku 4.5 $0.00006 $0.00292

Measured 5d ago against content hash b6bcb2130ba8, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade B, and why

ralph-convert-prd scanned grade B with 2 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 5d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Sends data to an external URLmediumData exfiltration

A POST to an outside endpoint may be telemetry or may be exfiltration; either way the mod talks to somewhere, and you should know where.

{ "command": "curl -s -X POST http://localhost:3000/api/tasks -H 'Content-Type: application/json' -d '{\"title\":\"test task\"}' -o /dev/null -w '%{http_code}'", "expect": "contains:201" }

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

| `backend` | Run tests + curl endpoint with real data | `curl -s http://localhost:3000/api/...` |
skills/ralph-convert-prd/SKILL.md · 300 lines

How it starts

The opening of the file, as written. The whole thing — 300 lines — stays where its author put it; the contents beside it link to each section on GitHub.

<quick_start>

  1. Read the user's PRD or feature requirements
  2. Read SPEC.md if available (for verification environment info)
  3. Break down into atomic user stories (one context window each)
  4. Classify each story with storyType
  5. Generate verificationCommands with real runtime checks
  6. Set blockedBy dependencies
  7. Order stories by dependency (schema → backend → UI → dashboard)
  8. Output valid tasks/prd.json </quick_start>

<essential_principles> Critical Rule: Each story must be completable in ONE Ralph iteration (one context window).

Stories that are too large cause the LLM to run out of context before completion, resulting in broken code.

Right-sized stories:

  • Add a database column
  • Create a UI component
  • Update server actions
  • Implement a filter

Too large (split these):

  • Build entire dashboards
  • Add authentication systems
  • Refactor entire APIs
  1. Schema/database changes
  2. Server actions and backend logic
  3. UI components
  4. Dashboard/summary views

Never reference something that doesn't exist yet.

Good criteria:

  • "Add status column with values: 'pending' | 'in_progress' | 'done'"
  • "Filter dropdown includes: All, Active, Completed"
  • "Clicking delete shows confirmation dialog"

Bad criteria (too vague):

  • "Works correctly"
  • "Good UX"
  • "Handles edge cases"

UI-focused stories MUST also include: "Verify in browser using Playwright e2e test"

By storyType:

storyType Required verification Example
database Run migration + query DB to confirm schema prisma migrate deploy, SQL query for new column
backend Run tests + curl endpoint with real data curl -s http://localhost:3000/api/...
api curl endpoint, check status code and response body curl -s -w '%{http_code}' ...
frontend Playwright e2e test that interacts with real UI npx playwright test tests/e2e/...
infra Health check, config validation, service startup curl -s http://localhost:3000/health
test Run the test suite npm test / pytest

Static checks (typecheck) are always included as baseline. Runtime validation is additionally required. </essential_principles>

<output_format>

{
  "project": "[Project Name]",
  "branchName": "ralph/[feature-name-kebab-case]",
  "description": "[Feature description]",
  "testCommands": {
    "unit": "npm test",
    "integration": "npm run test:integration",
    "e2e": "npx playwright test",
    "typecheck": "npm run typecheck"
  },
  "userStories": [
    {
      "id": "US-001",
      "title": "[Story title]",
      "description": "As a [user], I want [feature] so that [benefit]",
      "storyType": "database",
      "acceptanceCriteria": [
        "Specific criterion 1",
        "Specific criterion 2",
        "Typecheck passes"
      ],
      "verificationCommands": [
        { "command": "npm run typecheck", "expect": "exit_code:0" },
        { "command": "curl -s http://localhost:3000/api/tasks | jq length", "expect": "not_empty" }
      ],
      "status": "pending",
      "priority": 1,
      "attempts": 0,
      "maxAttempts": 3,
      "notes": "",
      "blockedBy": [],
      "docsToUpdate": ["README.md"],
      "completedAt": null,
      "lastAttemptLog": ""
    }
  ]
}

Read the full file on GitHub · 300 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 5d ago First seen · 300 lines · 57 tokens per session scan B b6bcb2130ba8

Subscribe to this mod's changes

ralph-convert-prd is a skill published in the GitHub repository cfircoo/claude-code-toolkit (17 stars, last pushed 5mo ago), licensed MIT. It adds 57 tokens to every session and 2,920 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it B with 2 findings (sends data to an external url, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens