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.
Overall
score
87%
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
100%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 well-crafted skill description that excels across all dimensions. It provides specific capabilities, includes explicit trigger terms users would naturally use, clearly answers both what and when, and has distinctive domain-specific terminology that prevents conflicts with other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Generate a Product Requirements Document (PRD)', 'Creates PRDs with user stories', 'converted to beads issues or prd.json for automated execution'. These are concrete, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both what (generate PRDs with user stories for ralph-tui task orchestration, convertible to beads issues or prd.json) and when (explicit 'Triggers on:' clause with multiple trigger phrases). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms explicitly listed: 'create a prd', 'write prd for', 'plan this feature', 'requirements for', 'spec out'. These are phrases users would naturally say when needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with specific domain context ('ralph-tui task orchestration', 'beads issues', 'prd.json'). The combination of PRD generation with this specific toolchain creates a clear niche unlikely to conflict with generic documentation skills. | 3 / 3 |
Total | 12 / 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 for PRD generation with clear workflows and excellent concrete examples. The main weakness is verbosity - the quality gates concept is over-explained, and the full example conversation adds significant length. The skill effectively teaches the PRD format and questioning process but could be more token-efficient.
Suggestions
Consolidate quality gates explanations - currently mentioned in Step 1, Step 2, the example, and the checklist; define once and reference
Consider moving the full example conversation to a separate EXAMPLES.md file and keeping just a brief example in the main skill
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some redundancy - the quality gates concept is explained multiple times, and the example conversation flow, while useful, is quite lengthy. Some sections could be tightened. | 2 / 3 |
Actionability | Highly actionable with concrete examples throughout: specific question formats with lettered options, exact PRD section templates, complete example conversation flow, and copy-paste ready markdown structures with proper formatting. | 3 / 3 |
Workflow Clarity | Clear multi-step workflow with explicit sequence (receive description → ask questions → generate PRD), adaptive decision points (when to ask follow-ups vs generate), and a final checklist for validation before output. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but everything is in one file. The lengthy example conversation and detailed PRD structure could potentially be split into separate reference files for cleaner navigation. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 13 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
Total | 13 / 16 Passed | |
- 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.