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

Passed

No findings from the security scan

Quality

Content

78%Weight 40%Scale 1-5

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

A well-structured overview that keeps the SKILL.md body lean and pushes detail to a single, real reference file, with a clear interactive workflow and confirmation checkpoints. Main improvements are de-duplicating the trigger list and adding an output-verification step after file generation.

Suggestions

Remove or compress the 'When to use this skill' bullet list since those triggers already appear verbatim in the frontmatter description, to recover tokens.

Add an explicit verification step after Step 2 (e.g., confirm each generated feature file exists at the agreed path and contains the filled template with no remaining [Current Date] placeholders).

Consolidate the 'Constraints' section with the per-step 'Step constraints' to avoid repeating the same MUST rules (date command, exact template wording, repeat 9-11) twice.

Dimension	Reasoning	Score
Conciseness	The body is efficient and assumes Claude's competence (no padding about what epics/features are), but the 'When to use' list duplicates the description's triggers and the 'What is covered', 'Constraints', and per-step constraints overlap, so a few tokens could be trimmed; not a 5.	4 / 5
Actionability	Gives concrete actionable steps and an executable command ('Run `date` before generation'), with clear sequencing; held at 4 because the exact template question wording and feature template are deferred to the reference rather than included inline.	4 / 5
Workflow Clarity	A clear numbered sequence (0 get date, 1 analyze+gather, 2 generate, 3 close) with confirmation checkpoints ('summarize it for confirmation', 'Wait for user responses before proceeding'); not a 5 because there is no post-generation verification of the output files.	4 / 5
Progressive Disclosure	A concise overview body with a single well-signaled, one-level-deep reference ('see [references/013-agile-feature.md]') that exists and holds the detailed templates and constraints; content is appropriately split and easy to navigate, matching the top anchor.	5 / 5
	Total	17 / 20 Passed

Description

91%Weight 40%Scale 1-5

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 clearly states what the skill does and when to trigger it, with varied natural trigger phrases. Minor room to sharpen action granularity and distinguish it from neighbouring agile-planning skills.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions ('split an epic into feature files', 'derive features with scope and acceptance criteria', 'plan feature documentation for stakeholders or engineering'), with only minor gaps in granularity; not quite the comprehensive multi-action coverage of a 5.	4 / 5
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 concrete trigger phrases, matching the top anchor.	5 / 5
Trigger Term Quality	Provides five natural phrasings users would actually 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'), covering strong synonym variation; the domain has no file-extension equivalent, so keyword coverage is comprehensive.	5 / 5
Distinctiveness Conflict Risk	Targets a clear niche (epic-to-feature documentation) with distinct triggers and minimal conflict risk; held at 4 rather than 5 because within a broader agile toolkit it could overlap with adjacent epic/story planning skills.	4 / 5
	Total	18 / 20 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/plinth
Path: skills/013-agile-feature/SKILL.md
Commit: 77b8825

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