prd-status
Check and update PRD status through lifecycle
67
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
32%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 description is too brief and lacks the explicit trigger guidance needed for Claude to reliably select it. While it identifies the PRD domain, it fails to explain what specific actions are performed, what 'lifecycle' means in this context, or when the skill should be invoked. The absence of a 'Use when...' clause significantly limits its utility in a multi-skill environment.
Suggestions
Add a 'Use when...' clause with trigger terms like 'PRD status', 'requirements document', 'update PRD', 'check requirements', 'document lifecycle'
Expand the capabilities to list specific actions such as 'mark PRD as draft/review/approved, track revision history, update completion percentage'
Include file type or format references if applicable (e.g., '.md PRD files', 'requirements documents in the /docs folder')
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (PRD status) and mentions two actions (check and update), but lacks comprehensive detail about what specific operations are performed or what 'lifecycle' entails. | 2 / 3 |
Completeness | Provides a weak 'what' (check and update status) but completely lacks any 'when' clause or explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Includes 'PRD' and 'status' which are relevant keywords, but misses common variations users might say like 'product requirements document', 'requirements doc', 'PRD tracking', or 'document status'. | 2 / 3 |
Distinctiveness Conflict Risk | PRD is somewhat specific, but 'status' and 'lifecycle' are generic terms that could overlap with other project management or document tracking skills. | 2 / 3 |
Total | 7 / 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 skill provides clear, actionable guidance for PRD status management with well-defined transition rules and validation steps. The workflow is explicit with good error handling coverage. However, it could be more concise by removing implementation tips that explain concepts Claude already knows, and could benefit from splitting detailed reference content into separate files.
Suggestions
Remove the 'Implementation Tips for Claude Code' section - Claude already understands state machines, path resolution, and atomic operations
Consider moving detailed metadata examples and error handling to a separate REFERENCE.md file, keeping SKILL.md as a concise overview
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably efficient but includes some unnecessary verbosity like 'Execution Instructions for Claude Code' header and 'Implementation Tips' section that explains concepts Claude already understands (state machines, atomic operations, path resolution). | 2 / 3 |
Actionability | Provides concrete YAML examples, specific status values, clear transition rules, and executable command examples. The output format and metadata update examples are copy-paste ready. | 3 / 3 |
Workflow Clarity | Clear 10-step sequence with explicit validation checkpoints (steps 1-4 validate before action). Error handling section provides feedback loops for common failure cases. Status transition rules are explicit. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but everything is inline in one file. The metadata updates, error handling, and implementation tips could be split into separate reference files for a cleaner overview. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 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.