ralph-tui-prd
Generate a Product Requirements Document (PRD) for ralph-tui task orchestration. Creates PRDs with user stories that can be converted to beads issues or prd.json for automated execution. Triggers on: create a prd, write prd for, plan this feature, requirements for, spec out.
88
84%
Does it follow best practices?
Impact
96%
1.52xAverage score across 3 eval scenarios
Passed
No known issues
Quality
Discovery
92%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong description that clearly communicates what the skill does (generates PRDs with user stories for ralph-tui) and when to use it (with explicit trigger phrases). The main weakness is that some trigger terms like 'plan this feature' and 'requirements for' are broad enough to potentially conflict with other planning or specification skills. The description is concise, uses third person voice correctly, and provides good context about output formats.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists specific concrete actions: 'Generate a Product Requirements Document (PRD)', 'Creates PRDs with user stories', 'converted to beads issues or prd.json for automated execution'. Multiple distinct outputs and formats are named. | 3 / 3 |
Completeness | Clearly answers both 'what' (generates PRDs with user stories convertible to beads issues or prd.json) and 'when' (explicit 'Triggers on:' clause with five specific trigger phrases). | 3 / 3 |
Trigger Term Quality | Includes explicit natural trigger phrases users would say: 'create a prd', 'write prd for', 'plan this feature', 'requirements for', 'spec out'. These cover common variations of how users would request this functionality. | 3 / 3 |
Distinctiveness Conflict Risk | The skill is fairly specific to 'ralph-tui task orchestration' and PRD generation, but terms like 'plan this feature' and 'requirements for' are somewhat generic and could overlap with general planning or requirements-gathering skills. The ralph-tui specificity helps but the broader triggers introduce some conflict risk. | 2 / 3 |
Total | 11 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured, highly actionable skill that clearly guides Claude through an iterative PRD creation process with concrete templates and a thorough worked example. Its main weakness is verbosity—the full example conversation and PRD take up significant space and some guidance is repeated across sections. The workflow is clear with good validation (checklist, adaptive questioning), but the monolithic structure could benefit from splitting the lengthy example into a separate file.
Suggestions
Move the full example conversation flow and PRD to a separate EXAMPLE.md file, keeping only a brief reference in the main skill to reduce token usage
Remove repeated guidance (e.g., 'be explicit and unambiguous' appears in both the User Stories section and the 'Writing for AI Agents' section)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly lengthy at ~200+ lines. The example conversation flow, while useful, is very long and could be trimmed. Some sections like 'Writing for AI Agents' repeat guidance already stated elsewhere (e.g., 'be explicit and unambiguous' appears multiple times). However, most content is instructional rather than explaining concepts Claude already knows. | 2 / 3 |
Actionability | The skill provides highly concrete, copy-paste-ready templates for question formats, PRD structure, output markers ([PRD]...[/PRD]), and a complete worked example with specific markdown formatting. Every section has explicit format examples and the checklist at the end is directly actionable. | 3 / 3 |
Workflow Clarity | The multi-step process is clearly sequenced (receive description → ask clarifying questions iteratively → generate PRD → wrap in markers). Adaptive questioning provides a feedback loop, the checklist at the end serves as a validation checkpoint, and the 'do NOT start implementing' constraint is explicit. The workflow handles the iterative nature of the task well. | 3 / 3 |
Progressive Disclosure | The content is entirely self-contained in one file with no references to external documents. While the structure uses clear headers and sections, the full example conversation flow and complete PRD example make this quite long. The example PRD could potentially be in a separate EXAMPLES.md file, and the detailed section descriptions could be split out for better organization. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- subsy/ralph-tui
- Commit
1d4670f
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.