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. Part of the skills-for-java project
89
86%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
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 clearly defines its purpose (agile feature documentation from epics), includes explicit 'Use when' triggers with natural agile terminology, and establishes a distinct niche. The description effectively communicates both capabilities and selection criteria, making it easy for Claude to choose this skill appropriately from a large skill set.
| 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'. Uses third person voice correctly. | 3 / 3 |
Completeness | Clearly answers both what ('creation of detailed agile feature documentation from an existing epic') and when ('Use when the user wants to split an epic into feature files, derive features with scope and acceptance criteria, or plan feature documentation'). | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'epic', 'feature files', 'acceptance criteria', 'feature documentation', 'stakeholders', 'engineering'. These are terms agile practitioners naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused on agile epic-to-feature decomposition with distinct triggers like 'epic', 'feature files', 'acceptance criteria'. The Java project context and specific agile terminology make it unlikely to conflict with generic documentation skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is well-organized and concise, appropriately delegating detailed content to a reference file. However, it lacks concrete examples of the question template, feature template format, and validation steps that would make it immediately actionable without consulting the reference file.
Suggestions
Include at least one example question from the template and one sample feature output snippet to make the skill more immediately actionable
Add explicit validation checkpoints (e.g., 'Confirm feature list with user before generating files', 'Verify date command succeeded before proceeding')
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, avoiding unnecessary explanations. It assumes Claude understands agile concepts and focuses only on the specific workflow and constraints needed. | 3 / 3 |
Actionability | Provides clear constraints and workflow steps, but lacks concrete examples of the feature template, question wording, or output format. The actual implementation details are deferred to a reference file. | 2 / 3 |
Workflow Clarity | The workflow sequence is outlined (intake → scope → refinement → generation), but lacks explicit validation checkpoints. No feedback loops for error recovery or verification steps before generating files. | 2 / 3 |
Progressive Disclosure | Appropriately structured with a concise overview and clear one-level-deep reference to the detailed guidance file. The split between SKILL.md overview and references/013-agile-feature.md is well-signaled. | 3 / 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
- jabrena/cursor-rules-java
- Commit
a886986
- 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.