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
64
75%
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 (splitting epics, deriving features), and includes explicit trigger phrases. The description is specific, well-structured, and occupies a distinct niche that minimizes conflict risk with other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | 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 trigger clause with 'Use when...' and a 'This should trigger for' section 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 | Occupies a clear niche: specifically about deriving features from epics in an agile context. The combination of 'epic', 'feature files', 'acceptance criteria', and 'agile' makes it highly distinct and unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
50%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill provides a reasonable high-level framework for an interactive epic-to-feature workflow, with clear constraints and a logical sequence. However, it delegates nearly all concrete, actionable content (template questions, feature document template, examples) to a reference file that cannot be verified, and the SKILL.md body itself lacks executable examples, validation checkpoints, and feedback loops that would make it robust and self-sufficient.
Suggestions
Include at least one concrete example of a template question and a snippet of the expected feature document output directly in the SKILL.md, so the skill is actionable even without the reference file.
Add an explicit validation/review checkpoint after generating each feature document (e.g., 'Present the generated feature to the user for review; incorporate feedback before proceeding to the next feature').
Remove the 'What is covered in this Skill?' bullet list, which largely duplicates the workflow section and constraints, to improve conciseness.
Provide the bundle reference file (references/013-agile-feature.md) or inline the critical template content so the skill is not entirely dependent on an unverifiable external file.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is moderately efficient but includes some redundancy—constraints are partially restated in the workflow section, and phrases like 'This is an interactive SKILL' and the 'What is covered' bullet list add tokens without much value beyond what the workflow already conveys. | 2 / 3 |
Actionability | The skill provides a structured workflow and clear constraints, but lacks concrete examples of the template questions, the feature document template, or executable commands beyond `date`. The actual actionable content (questions, template) is deferred entirely to the reference file, leaving the SKILL.md itself with only abstract guidance. | 2 / 3 |
Workflow Clarity | The workflow has a clear sequence (get date → analyze epic → generate docs → close), but lacks explicit validation checkpoints—there's no step to verify generated feature files against acceptance criteria, no feedback loop for user review/correction of individual feature documents before proceeding, and no error recovery guidance. | 2 / 3 |
Progressive Disclosure | The skill references a single detailed file (references/013-agile-feature.md) which is good one-level-deep disclosure, but since no bundle files were provided, we cannot verify the reference exists or is well-structured. Additionally, too much critical content (the actual template questions, the feature document template) appears to live entirely in the reference file, making the SKILL.md itself incomplete as a standalone overview. | 2 / 3 |
Total | 8 / 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
3b97275
- 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.