CtrlK
BlogDocsLog inGet started
Tessl Logo

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

70

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

72%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, interactive single-purpose skill with clear sequencing and clean progressive disclosure, weakened by some redundant/conceptual padding and the absence of any validation step for the generated artifact.

Suggestions

Remove the 'An epic represents a large body of work...' definitional sentence and deduplicate the get-date and read-template-fresh items that appear in both Constraints and Workflow.

Inline the core question template (or a compact summary of it) so the gather step is actionable without requiring the reference, or explicitly state which reference section to read at step 1.

Add a validation checkpoint after step 2 — e.g., confirm every required section and date placeholder is present in the generated epic before delivering it.

DimensionReasoningScore

Conciseness

Mostly efficient with clear sections, but explains what an epic is ('An epic represents a large body of work...') that Claude already knows, and the Constraints and Workflow steps redundantly repeat the same MANDATORY/MUST items (get date, read template fresh).

2 / 3

Actionability

Gives a concrete command (`date`) and names required document sections, but the actual question content is delegated to the reference and the generate step stays high-level ('Create the epic Markdown with all required sections'), so it is not fully copy-paste ready.

2 / 3

Workflow Clarity

A clear 0→3 sequence with explicit wait-for-response checkpoints is present, but there is no validation or feedback loop verifying the generated epic, leaving the validation dimension the rubric associates with score 3 unmet.

2 / 3

Progressive Disclosure

The body is a concise overview with well-organized sections and a single one-level-deep, clearly signaled reference (references/012-agile-epic.md) that exists in the bundle, matching the score-3 anchor.

3 / 3

Total

9

/

12

Passed

Description

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.

A strong, third-person description that concisely states concrete capabilities, provides explicit 'Use when' triggers plus natural trigger phrases, and is clearly distinct from other skills.

DimensionReasoningScore

Specificity

Names multiple concrete actions — 'creation of agile epics with comprehensive definition including business value, success criteria, and breakdown into user stories' — matching the score-3 anchor listing several specific actions.

3 / 3

Completeness

Explicitly answers both what ('Guides the creation of agile epics...') and when ('Use when the user wants to create an agile epic, define large bodies of work...') with explicit triggers, matching the score-3 anchor.

3 / 3

Trigger Term Quality

Covers natural phrases users would say — 'Create an agile epic', 'Write an epic', 'I need to create an epic', 'Define an epic', 'Epic definition' — giving good coverage of common variations.

3 / 3

Distinctiveness Conflict Risk

Occupies a clear niche (agile epics) with distinct triggers unlikely to fire for unrelated skills; written in third person ('Guides'), satisfying the voice rule.

3 / 3

Total

12

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
jabrena/cursor-rules-java
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.