CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

create-epics

Turns the GDDs and architecture into epics, one per architectural module. Use when the user wants to break the game into epics or plan the work before writing stories. Not for splitting one epic into stories.

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

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

An exceptionally operational skill: every phase has concrete commands, verbatim outputs, explicit validation gates, and per-write confirmation, with conditional loading of the only external reference. The sole trimmable cost is mild redundancy in restating the one-question-per-epic rule.

Suggestions

State the one-ask-per-epic rule once in Phase 3 and reference it from Phase 5 instead of repeating it, saving a few lines without losing the guardrail.

DimensionReasoningScore

Conciseness

The body is dense and entirely project-specific with no explanation of concepts Claude already knows, but the ask-one-epic-at-a-time rule is restated three times across Phases 3 and 5 ("Never fold several epics into one question", "A yes covers the epic it answers, and only that one", "This is its own ask, one per epic") and could be consolidated.

4 / 5

Actionability

Everything is executable: verbatim report blocks, exact question wording with option lists, runnable scripts (gdd-structure-check.sh, md-section.sh, adr-status.sh, write-guard.sh), and copy-paste-ready EPIC.md and index templates with placeholder conventions.

5 / 5

Workflow Clarity

Six phases are explicitly sequenced with a copy-and-tick checklist, hard stop conditions ("N is 0: stop"), write validation (write-guard.sh before every write, OVERWRITE handling), and error-recovery feedback loops (a dismissed question is re-asked; an existing EPIC.md triggers an update-in-place ask).

5 / 5

Progressive Disclosure

The bundle's one reference (references/pr-epic-gate.md) is clearly signaled and conditionally loaded ("On a skip, do not load it"), is one level deep, and verified to exist; always-needed workflow content and templates stay inline where they belong.

5 / 5

Total

19

/

20

Passed

Description

82%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 well-crafted description with explicit what/when structure and an explicit exclusion clause that sharply reduces conflict risk with adjacent skills. Its only weakness is that it compresses the skill's work into one described action instead of enumerating the concrete outputs it produces.

Suggestions

Enumerate 2-3 concrete actions in the description, e.g. "Turns the GDDs and architecture into epics, one per architectural module: writes production/epics/[slug]/EPIC.md, builds the epics index, and flags requirements with no Accepted ADR."

Add a common synonym trigger such as "divide the game into epics" or "plan the work" alongside the existing "break the game into epics" phrasing to broaden natural keyword coverage.

DimensionReasoningScore

Specificity

"Turns the GDDs and architecture into epics, one per architectural module" names a single concrete transformation with its inputs and output granularity, but the description lists only that one action rather than the several specific actions (e.g. writes each EPIC.md, builds the epics index, checks ADR coverage) that anchor 4 requires.

3 / 5

Completeness

The what ("Turns the GDDs and architecture into epics, one per architectural module") and the when ("Use when the user wants to break the game into epics or plan the work before writing stories") are both explicit, with concrete trigger phrases and an additional negative boundary clause.

5 / 5

Trigger Term Quality

"break the game into epics" and "plan the work before writing stories" are natural user phrasings with the key term "epics" present, though common variations like "divide the game into epics" or "work breakdown" are missing.

4 / 5

Distinctiveness Conflict Risk

"Not for splitting one epic into stories" explicitly disambiguates this skill from the sibling story-splitting skill, and the GDD/architecture-driven epic niche is distinct, leaving minimal conflict risk.

5 / 5

Total

17

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

14

/

16

Passed

Repository

Donchitos/Claude-Code-Game-Studios

Path

.claude/skills/create-epics/SKILL.md

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.