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

76%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/013-agile-feature/SKILL.md

Quality

Content

57%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.

The body presents a clear, appropriately interactive workflow with proper deferral of detail to a single reference file, but it suffers from redundant sections, a missing post-generation validation step for the batch file creation, and a dangling nested reference to a nonexistent template asset. Tightening the duplication and adding an output-verification checkpoint would raise it substantially.

Suggestions

Add a post-generation validation step (Step 3+) that verifies each feature file: naming convention followed, all [Current Date] and other placeholders replaced, and per-feature answers (stories, dependencies, metrics) incorporated — this is a batch operation and currently has no feedback loop.

Remove the redundancy between the 'What is covered in this Skill?', 'When to use this skill', and 'Constraints' sections, and the repeated step constraints inside the Workflow — the trigger list already lives in the description.

Fix the dangling second-level reference: the reference file includes assets/agile-feature-template.md via xi:include but no assets/ directory exists in the bundle — either add the template file or inline the template content into references/013-agile-feature.md.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean but carries real redundancy: the "What is covered in this Skill?" bullets, the "When to use this skill" list (a verbatim duplicate of the description's triggers), and the Constraints block overlap heavily, and the date/exact-wording constraints are repeated inside the Workflow steps. This is tighter than the padded anchor 2, but the duplication exceeds the 'minor instances' of anchor 4.	3 / 5
Actionability	Instructions are concrete and executable for an instruction-only skill: "Run `date` before generation", "summarize it for confirmation, then ask the template questions in order", "Create one Markdown feature file per agreed feature", with the question template and feature template correctly deferred to references/013-agile-feature.md. It is not a 5 because no inline example of the output or template shape is given, leaving a minor gap in copy-paste-ready guidance.	4 / 5
Workflow Clarity	Steps 0–3 are clearly sequenced with user-confirmation checkpoints ("summarize it for confirmation", "Wait for user responses before proceeding"), but generating one file per feature is a batch operation with no validation step for the output (e.g., verifying placeholders/dates were replaced and naming was followed), which caps this at 3 per the rubric's batch-operation rule. It is above a 2 because the sequence and confirmations are explicit.	3 / 5
Progressive Disclosure	The body is a well-sectioned overview pointing clearly to a real one-level reference (references/013-agile-feature.md), but scoring against the actual bundle reveals that the reference's feature template is an xi:include of assets/agile-feature-template.md, which does not exist in the bundle (no assets/ directory), making the deepest content unreachable. This is a more-than-minor organization gap, so it sits below the good-structure anchor 4.	3 / 5
	Total	13 / 20 Passed

Description

83%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 description with third-person voice, concrete capabilities, and an explicit 'Use when' trigger clause backed by natural user phrasings. Its only weaknesses are modest: slightly incomplete action coverage and minor overlap risk with sibling agile-documentation skills in the same toolkit.

Dimension	Reasoning	Score
Specificity	The description lists several 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", "plan feature documentation"), with only minor gaps such as the interactive/template-driven nature of the workflow. It falls short of a 5 because coverage is not comprehensive (nothing about the structured Q&A or per-feature refinement loop).	4 / 5
Completeness	It explicitly answers both what ("Guides the creation of detailed agile feature documentation from an existing epic") and when ("Use when the user wants to…" plus "This should trigger for requests such as…" with concrete trigger phrases). This matches the anchor for a clear, explicit what-and-when with concrete triggers; a 4 would require the 'when' to be less explicit than it is here.	5 / 5
Trigger Term Quality	It includes natural user phrasings with variations ("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"). A few natural terms are missing (e.g., "feature breakdown", "user stories", file extensions), keeping it below the comprehensive synonym coverage of a 5.	4 / 5
Distinctiveness Conflict Risk	The epic-to-features niche has distinct, specific triggers unlikely to fire for unrelated skills. However, "Part of Plinth Toolkit" signals a family of sibling agile skills (e.g., epic creation, user-story breakdown) with minor overlap risk on closely related requests, keeping it just below the minimal-conflict 5.	4 / 5
	Total	17 / 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: dca88dc

Reviewed: 3 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.