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; Break down an agile epic into deliverable features. Part of Plinth Toolkit

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

70%

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

A well-organized interactive skill body with a clear sequenced workflow, explicit confirmation checkpoints, and clean single-level progressive disclosure. It loses points on conciseness due to redundant preview/trigger sections and on actionability because the executable templates live only in the reference.

Suggestions

Remove the 'When to use this skill' list from the body since it duplicates the description's trigger phrases, or replace it with a one-line pointer.

Collapse the 'What is covered in this Skill?' preview into the Workflow section to eliminate overlap with the steps that follow.

Inline the numbered questions template (or a compact summary of questions 1-11) so the body is executable without opening the reference, keeping the full feature template in references/.

Dimension	Reasoning	Score
Conciseness	The body is largely lean and avoids explaining concepts Claude already knows, but the 'What is covered in this Skill?' preview and the 'When to use this skill' list largely duplicate the workflow and the description's triggers, adding tokens that could be trimmed.	2 / 3
Actionability	Step-level guidance is concrete ('Run `date` before generation', 'ask the template questions in order', 'Create one Markdown feature file per agreed feature'), but the actual question template and feature template are deferred to the reference, so the body alone is missing key executable detail.	2 / 3
Workflow Clarity	A clear numbered sequence (0-3) with an explicit confirmation checkpoint ('summarize it for confirmation'), a 'Wait for user responses before proceeding' gate, and a repeat loop for per-feature questions (9-11), plus a MANDATORY/MUST constraint checklist.	3 / 3
Progressive Disclosure	The body is a concise overview that points to a single, verified one-level-deep reference ([references/013-agile-feature.md]), with clear signaling and no nested reference chains.	3 / 3
	Total	10 / 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, well-structured description that clearly states capabilities, supplies multiple natural trigger phrases, and explicitly covers both what and when. It is specific to the agile feature-decomposition niche with low conflict risk.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'creation of detailed agile feature documentation from an existing epic', 'split an epic into feature files, derive features with scope and acceptance criteria' — rather than vague language.	3 / 3
Completeness	Explicitly answers both what ('Guides the creation of detailed agile feature documentation from an existing epic') and when ('Use when the user wants to...', 'This should trigger for requests such as...') with explicit triggers.	3 / 3
Trigger Term Quality	Provides good coverage of natural phrasings a user would say: 'Create features from an epic; Split epic into features; Feature files from epic; Derive features from epic; Break down an agile epic into deliverable features'.	3 / 3
Distinctiveness Conflict Risk	Occupies a clear epic-to-feature decomposition niche with distinct triggers ('split an epic into feature files', 'Derive features from epic') and a namespace cue ('Part of Plinth Toolkit'), making wrong-skill triggering 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
Path: skills/013-agile-feature/SKILL.md
Commit: fdaf68c

Reviewed: about 4 hours 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.