012-agile-epic
Guides the creation of agile epics with comprehensive definition including business value, success criteria, and breakdown into user stories. Use when the user wants to create an agile epic, define large bodies of work, break down features into user stories, or document strategic initiatives. This should trigger for requests such as Create an agile epic; Write an epic; I need to create an epic; Define an epic; Epic definition. 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/012-agile-epic/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 defines what the skill does (guides agile epic creation with specific deliverables), when to use it (explicit trigger clause with natural language examples), and occupies a distinct niche. The inclusion of example trigger phrases further strengthens its selectability. The 'Part of cursor-rules-java project' suffix is unnecessary metadata but doesn't significantly detract.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'creation of agile epics', 'business value', 'success criteria', 'breakdown into user stories'. These are concrete, domain-specific capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (guides creation of agile epics with business value, success criteria, user story breakdown) and 'when' (explicit 'Use when...' clause with multiple trigger scenarios and example phrases). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms: 'create an agile epic', 'write an epic', 'define an epic', 'epic definition', 'break down features into user stories', 'strategic initiatives', 'large bodies of work'. These are terms users would naturally say. | 3 / 3 |
Distinctiveness Conflict Risk | Clearly occupies a distinct niche around agile epics specifically. The trigger terms are specific enough ('epic', 'user stories', 'agile') that it would be unlikely to conflict with general project management or other development 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.
This skill provides a reasonable high-level framework for creating agile epics interactively, with a clear workflow sequence and appropriate constraints. However, it relies heavily on an external reference file that isn't provided in the bundle, making the skill incomplete on its own. The content includes some verbosity explaining concepts Claude already knows and lacks concrete examples, validation steps, and error handling.
Suggestions
Add a concrete example of a completed epic output (even abbreviated) so Claude knows the expected format without relying solely on the external reference file.
Include at least 2-3 sample questions from the template inline so the skill is partially actionable even if the reference file is unavailable.
Add a validation checkpoint after document generation (e.g., 'Verify all sections are populated and no placeholders remain') to improve workflow robustness.
Remove the explanatory text about what an epic is and the 'What is covered' bullet list, as these are redundant with the workflow steps and Claude already understands agile concepts.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary explanation (e.g., 'An epic represents a large body of work that can be broken down into smaller user stories, features, or tasks' and the 'What is covered' section) that Claude already knows. The constraints section has some redundancy between MANDATORY/MUST items. Could be tightened. | 2 / 3 |
Actionability | The workflow provides a structured sequence but lacks concrete examples of the actual questions to ask, the template format, or a sample epic output. The skill heavily depends on a reference file (references/012-agile-epic.md) for the actual actionable content, and that file is not provided in the bundle, making the skill itself incomplete in terms of executable guidance. | 2 / 3 |
Workflow Clarity | The workflow has a clear sequence (get date → gather info → generate document → follow-up), but lacks validation checkpoints. There's no verification step to confirm the generated epic is complete or correct, no feedback loop for missing information, and no explicit handling of what happens if the user provides incomplete answers. | 2 / 3 |
Progressive Disclosure | The skill references a detailed guide at references/012-agile-epic.md which is a good one-level-deep reference, but the bundle files show no such file exists. The SKILL.md itself includes content that could be more concisely organized (the 'What is covered' list duplicates what the workflow describes). The reference path accuracy cannot be verified. | 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.