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
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/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 its purpose, lists concrete capabilities, and provides explicit trigger guidance with example phrases. The 'Use when...' clause is comprehensive and includes natural language variations. The only minor note is the trailing 'Part of cursor-rules-java project' which adds little selection value but doesn't detract significantly.
| 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
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 creating agile epics but lacks concrete, actionable content. Nearly all specifics—the actual question template, example outputs, and detailed constraints—are deferred to a reference file, leaving the SKILL.md body too abstract to be independently useful. The workflow is sequenced but missing validation steps and concrete examples.
Suggestions
Include at least a summary of the key questions from the template directly in the SKILL.md so the skill is actionable without requiring the reference file
Add a concrete example of expected epic output (even abbreviated) to make the 'Generate epic document' step actionable
Remove the 'What is covered in this Skill?' bullet list and the definition of an epic—these are redundant and Claude already understands these concepts
Add a validation checkpoint after information gathering (e.g., 'Confirm all required fields are populated before generating the document')
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary explanation (e.g., defining what an epic is, the 'What is covered' section listing obvious items). The bullet list of covered topics is largely redundant given the workflow section. However, it's not excessively verbose. | 2 / 3 |
Actionability | The skill is vague and abstract—it says to 'ask template questions in strict order' and 'generate epic Markdown with all required sections' but provides no actual template, no example questions, no example output, and no concrete format. The only concrete command is `date`. Everything actionable is deferred to the reference file. | 1 / 3 |
Workflow Clarity | Steps are listed in a clear sequence (get date → gather info → generate document → follow-up), but there are no validation checkpoints, no feedback loops for incomplete or unclear user responses, and no explicit criteria for when to proceed between steps. The workflow is more of an outline than a detailed process. | 2 / 3 |
Progressive Disclosure | There is a reference to a detailed file (references/012-agile-epic.md) which is good one-level-deep disclosure. However, the SKILL.md itself is too thin—it defers almost all actionable content to the reference file, making the skill body insufficient on its own. The balance between overview and reference is off. | 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.