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. This should trigger for requests such as Create features from an epic; Split epic into features; Feature files from epic; Derive features from epic. Part of cursor-rules-java project

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

57%

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

The body is a well-organized interactive-workflow overview with good progressive disclosure to a single real reference, but it is held back by redundant trigger/constraint repetition and by deferring the actual question and feature templates — the core actionable content — to the reference file.

Suggestions

Remove the duplicate 'When to use this skill' trigger list (already in the description) and consolidate the repeated per-feature-repeat constraint into one place to tighten conciseness.

Inline the numbered question template (at least questions 9-11) and the feature document template, or summarize their key fields in the body, so the skill is actionable without requiring the reference.

Add a brief validate-fix-retry or per-feature completion checkpoint to the workflow so multi-feature generation has an explicit feedback loop.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean and avoids explaining concepts Claude knows, but the trigger phrases are duplicated between the description and the 'When to use this skill' section, and the per-feature-repeat constraint is stated redundantly in both Constraints and Step 1, so it could be tightened.	2 / 3
Actionability	Process guidance is concrete (numbered workflow, MUST/MANDATORY constraints, 'Run date'), but the actual numbered question template and feature template — the most actionable content — are deferred to the reference rather than included inline, leaving key details absent from the body.	2 / 3
Workflow Clarity	A clear numbered sequence (0-3) with ordering constraints and a user-confirmation checkpoint is present, but there is no explicit validate-fix-retry feedback loop, and per-feature iteration is described rather than rendered as a concrete looping checklist.	2 / 3
Progressive Disclosure	The body is a concise overview that points to a single, clearly signaled, one-level-deep reference (references/013-agile-feature.md) which exists on disk, matching the well-signaled one-level-deep 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.

The description is third-person, concise, and strongly structured with an explicit 'Use when' clause and concrete natural-language triggers. It clearly communicates both capability and invocation conditions with low conflict risk.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'split an epic into feature files', 'derive features with scope and acceptance criteria', 'plan feature documentation for stakeholders or engineering' — matching the multiple-specific-actions anchor rather than the domain-plus-some-actions level 2.	3 / 3
Completeness	Explicitly answers both what (creation of agile feature documentation from an epic) and when via an explicit 'Use when...' clause plus example triggers, satisfying the level-3 anchor.	3 / 3
Trigger Term Quality	Provides natural phrasings a user would actually say — 'Create features from an epic; Split epic into features; Feature files from epic; Derive features from epic' — giving good coverage of common variations.	3 / 3
Distinctiveness Conflict Risk	Targets a distinct epic-to-feature niche with specific agile triggers and is scoped by 'Part of cursor-rules-java project', making broad conflicts unlikely.	3 / 3
	Total	12 / 12 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: jabrena/cursor-rules-java
Commit: 159e7ce

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.