CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

spek-implement-epic

Implement every planned spec of an epic in one request, running the standard implement workflow for each spec through separate agents, each in its own git worktrees, in dependency order. Use for "implement this epic", "build the epic", or "implement <epic name>".

Quality

90%

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

88%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 high-quality orchestration body: fully executable commands with exact payloads, a clearly sequenced loop with validation checkpoints, error-recovery feedback loops, and precise hand-back contracts. The only deductions are minor trimmable rationale passages with dated detail and inline content that could move to reference files.

DimensionReasoningScore

Conciseness

The body is dense operational prose where nearly every sentence carries commands, states, or refusal handling, but a few spots could be trimmed: the headless-session rationale embeds a dated version record ("recorded on 2026-10-24 with Claude Code 2.1.310") and Step 2 explains dirty-repo mechanics partly inferable from context.

4 / 5

Actionability

Fully executable throughout: exact CLI invocations with complete JSON payloads (status/worktree/merge/implement new/spec amend), exact first-line hand-back markers (DONE:/QUESTION:/FAILED:), and concrete handling for named error codes like epic_merge_conflict and merge_lock_timeout.

5 / 5

Workflow Clarity

Steps 1–8 form a clear, explicitly looped sequence with validation checkpoints and feedback loops: refuse-before-start on epic.run.problems, merge retry on merge_lock_timeout, cut-off child detection and escalation, stopping mode, and a final-report checklist — thorough validation for a batch operation.

5 / 5

Progressive Disclosure

With no bundle files present, the body's own structure scores well: numbered steps, bold headers, and an explicit loop map with nothing buried or nested. Minor gaps: sections like the child-prompt template and headless/trace-span guidance are long enough to live in a reference file, and at ~135 lines the skill exceeds the sub-50-line simple-skill exception.

4 / 5

Total

18

/

20

Passed

Description

88%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: it states exactly what the skill does at a mechanical level (specs, agents, worktrees, dependency order) and pairs it with an explicit Use-for clause of natural trigger phrases. The only gaps are modest trigger-synonym coverage and slight overlap risk with the sibling single-spec implement skill.

DimensionReasoningScore

Specificity

The description specifies multiple concrete actions — implementing every planned spec of an epic in one request via the standard implement workflow, through separate agents, each in its own git worktrees, in dependency order — giving comprehensive, mechanism-level coverage.

5 / 5

Completeness

Both questions are explicitly answered: the first sentence states precisely what the skill does, and an explicit "Use for ..." clause lists concrete trigger phrases for when to invoke it.

5 / 5

Trigger Term Quality

The explicit triggers ("implement this epic", "build the epic", "implement <epic name>") are natural phrasings a user would say, but coverage lacks synonyms or variations such as "run the epic" or "finish the epic".

4 / 5

Distinctiveness Conflict Risk

A clear niche (epic-scoped orchestrated implementation) with distinct epic-named triggers, but minor overlap risk with the closely related single-spec implement skill that shares "implement" trigger language.

4 / 5

Total

18

/

20

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

nicholasjackson/tcgreplay

Path

skills/spek-implement-epic/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.