CtrlK
BlogDocsLog inGet started
Tessl Logo

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

76

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Advisory

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Content

87%

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 concise, actionable overview that defers detail to a single existing reference, with a clearly sequenced workflow. Its main weakness is workflow clarity: verification checkpoints are implicit and the batch file-generation step lacks an explicit validation or feedback loop.

Suggestions

Add an explicit validation checkpoint after generating feature files (e.g., verify each file was written, that all [Current Date] placeholders were replaced, and that the count matches the agreed feature list) before closing with integration guidance.

Surface an error-recovery loop for the generation step — what to do if a feature is missing required inputs or a date placeholder remains unfilled.

Make the epic-confirmation checkpoint explicit in the workflow steps (e.g., 'Do not proceed to Step 2 until the user confirms the epic summary and feature list') rather than only implying it through the constraints.

DimensionReasoningScore

Conciseness

The body is lean and organized with no padding or explanations of concepts Claude already knows; every section (overview, constraints, workflow, reference) earns its place.

3 / 3

Actionability

Provides concrete executable guidance for an instruction skill — a specific command ('Run `date` before generation'), explicit step ordering, and clear directives like 'Read epic content from file path or pasted input—do not invent epic details'.

3 / 3

Workflow Clarity

Steps are clearly sequenced (Step 0–3) and interaction order is spelled out, but verification checkpoints are implicit (relying on user confirmation) and the multi-file generation step has no explicit validation or error-recovery loop.

2 / 3

Progressive Disclosure

A clear overview with a single, well-signaled one-level-deep reference ('see references/013-agile-feature.md') that exists as a real bundle file; content is appropriately split.

3 / 3

Total

11

/

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 specific, trigger-rich, and complete, explicitly stating both capabilities and when to use the skill in natural user language. It is clearly distinguishable from other skills.

DimensionReasoningScore

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' — rather than vague language.

3 / 3

Completeness

Clearly answers both 'what' ('Guides the creation of detailed agile feature documentation from an existing epic') and 'when' via an explicit 'Use when...' clause plus 'This should trigger for requests such as...'.

3 / 3

Trigger Term Quality

Includes natural phrasings a user 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'), giving good coverage of common variations.

3 / 3

Distinctiveness Conflict Risk

Occupies a clear niche (epic-to-feature breakdown) with triggers tied to epics and features, making it unlikely to fire for unrelated skills.

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/plinth
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.