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
74
67%
Does it follow best practices?
Impact
Pending
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 specific capabilities, includes natural trigger terms, and explicitly addresses both what the skill does and when to use it. The domain is well-scoped to agile feature documentation from epics, making it highly distinctive. The 'Part of the skills-for-java project' note is minor metadata that doesn't detract from the description's quality.
| 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 'Use when' clause covering splitting epics, deriving features, and planning feature documentation). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'epic', 'feature files', 'acceptance criteria', 'agile', 'feature documentation', 'stakeholders', 'engineering'. These cover the domain well and match how users naturally describe this work. | 3 / 3 |
Distinctiveness Conflict Risk | Highly specific niche: agile feature documentation derived from epics. The combination of 'epic', 'feature files', 'acceptance criteria', and 'agile' creates a distinct trigger profile 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 outline of an interactive epic-to-feature workflow but critically lacks actionable content—no templates, no example questions, no sample output, and no concrete commands beyond a vague mention of using `date`. Nearly all useful content is deferred to a reference file, making the SKILL.md itself insufficient as a standalone guide.
Suggestions
Include the actual numbered questions (or at least a representative subset) directly in the SKILL.md so the workflow is actionable without requiring the reference file.
Add the feature Markdown template or at least a concrete example of expected output for one feature file.
Provide an explicit numbered workflow with validation steps (e.g., 1. Read epic → 2. Confirm summary with user → 3. Ask scoping questions → 4. For each feature, ask questions 9-11 → 5. Generate files → 6. Confirm output with user).
Include the actual `date` command usage example (e.g., `date '+%Y-%m-%d'`) rather than just mentioning it abstractly.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly efficient but includes some unnecessary enumeration of what's covered that could be tightened. The bullet list under 'What is covered' is somewhat redundant given the constraints section and reference file. | 2 / 3 |
Actionability | No concrete code, commands, templates, or executable examples are provided. The skill describes what to do abstractly ('use the feature template', 'use exact wording from the questions template') but never shows the template, the questions, or any concrete output format. Everything actionable is deferred to the reference file. | 1 / 3 |
Workflow Clarity | There is an implicit sequence (read epic → ask questions in order → repeat 9-11 per feature → generate files), but no explicit numbered workflow with validation checkpoints. The mention of 'questions 9-11' without showing them makes the flow hard to follow from this file alone. | 2 / 3 |
Progressive Disclosure | There is a reference to a detailed file (references/013-agile-feature.md) which is good one-level-deep disclosure, but the SKILL.md itself lacks enough substance to serve as a useful overview—it's too thin to stand alone and too dependent on the reference file for all actionable content. | 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
1847adc
- 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.