013-agile-feature
Guides the creation of detailed agile feature documentation from an existing epic. Use when the user wants to split an epic into feature files, derive features with scope and acceptance criteria, or plan feature documentation for stakeholders or engineering. This should trigger for requests such as Create features from an epic; Split epic into features; Feature files from epic; Derive features from epic. Part of cursor-rules-java project
74
67%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/013-agile-feature/SKILL.mdQuality
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 strong skill description that clearly articulates what the skill does (creates agile feature documentation from epics), when to use it (explicit trigger clause with multiple natural phrasings), and occupies a distinct niche. The inclusion of both a 'Use when' clause and a 'This should trigger for' clause with concrete example requests provides excellent guidance for skill selection.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description lists multiple specific concrete actions: 'split an epic into feature files', 'derive features with scope and acceptance criteria', 'plan feature documentation for stakeholders or engineering'. These are clear, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (guides creation of detailed agile feature documentation from an existing epic) and 'when' (explicit 'Use when' clause plus a 'This should trigger for' clause listing specific request patterns). | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms that users would actually say: 'split epic into features', 'feature files from epic', 'derive features from epic', 'create features from an epic', 'acceptance criteria', 'feature documentation'. Good coverage of natural variations. | 3 / 3 |
Distinctiveness Conflict Risk | The description carves out a clear niche: agile feature documentation derived specifically from epics. The combination of 'epic', 'feature files', 'acceptance criteria', and 'agile' terminology makes it highly distinct and unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
35%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides a reasonable high-level structure for an interactive epic-to-features workflow, but critically lacks the concrete content needed for execution. The template questions and feature document template—which are the core of the skill—are entirely absent from the body and deferred to a reference file, making the SKILL.md more of an abstract outline than actionable guidance. Adding at minimum the question template and an example feature output would significantly improve utility.
Suggestions
Include the actual numbered template questions (1-11) inline or at minimum show the per-feature questions (9-11) so the skill is actionable without requiring the reference file.
Add a concrete example of a generated feature document (even abbreviated) showing the expected Markdown structure, headers, and placeholder content.
Add a validation checkpoint after feature generation—e.g., 'Present feature summary to user for approval before writing files' to ensure correctness.
Remove duplicated constraints between the Constraints section and Workflow step constraints to improve conciseness.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably concise but includes some redundancy—constraints are repeated between the Constraints section and the Workflow steps (e.g., 'Use exact wording from the numbered template questions' appears twice). The 'What is covered' bullet list is somewhat redundant with the workflow itself. | 2 / 3 |
Actionability | The skill lacks concrete, executable guidance. It references 'template questions' and a 'feature template' but never shows them—they are entirely deferred to a reference file. There are no example outputs, no sample feature document structure, no actual question text, and no copy-paste ready content. The workflow steps are abstract descriptions rather than actionable instructions. | 1 / 3 |
Workflow Clarity | The workflow has a clear sequence (get date → analyze epic → generate docs → close), but validation checkpoints are missing. There's no step to verify generated features against the epic scope, no review/approval gate before finalizing documents, and no error recovery guidance if the user rejects a feature summary. | 2 / 3 |
Progressive Disclosure | There is a reference to a detailed file (references/013-agile-feature.md) which is good one-level-deep disclosure. However, too much critical content (the actual template questions, the feature document template) is deferred to that file, leaving the SKILL.md without enough standalone actionability. The overview doesn't give enough to be useful on its own. | 2 / 3 |
Total | 7 / 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
- jabrena/cursor-rules-java
- Commit
899d988
- 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.