CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

spec-feature

Spec a new feature — recall architecture knowledge, create a spec document, build an implementation plan, and break into tasks.

Quality

72%

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

Fix and improve this skill with Tessl

tessl review fix ./devflow-plugin/skills/spec-feature/SKILL.md

The canonical home for this skill is spec-feature in AndreJorgeLopes/devflow

SKILL.md
Quality
Evals
Security

Quality

Content

75%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 is a strongly actionable, well-sequenced workflow with concrete commands, templates, and user-confirmation gates, scoring at the top of the actionability scale. Its weaknesses are moderate verbosity in the handoff and diagram sections and the absence of any reference files to move the large spec template and handoff detail out of the main file.

Suggestions

Trim or offload the step-8 handoff mechanics (spawned-session, worktree, sidebar details) — that behavior belongs to the handoff skill; a one-line summary of what invoking it does would suffice.

Move the full spec document template to a references/spec-template.md file and reference it from step 4 to shorten SKILL.md and support progressive disclosure.

Add an explicit revise loop after step 6 (e.g., "if the user requests changes, update the spec and re-present") to close the workflow-clarity validation gap.

DimensionReasoningScore

Conciseness

The body is mostly imperative and efficient (concrete regex, bash snippet, terse steps), but includes unnecessary padding: the step-8 paragraph detailing spawned-session/worktree/sidebar mechanics of another skill, and the dense diagram-complexity rules, over-explain what Claude could do with less. Fits 'mostly efficient but could be tightened' rather than 4, whose over-explanation would be only minor.

3 / 5

Actionability

Fully executable guidance throughout: a concrete regex `[A-Z]+-[0-9]+`, a copy-paste bash title-setting command, the exact output path `docs/specs/<feature-name>.md` with a complete spec template, exact tool invocations with JSON/flag arguments (`mark_chapter`, `devflow:phase-handoff --phase spec --next-phase plan`), and a ready markdown embed snippet. Matches the top anchor for copy-paste-ready commands covering the common cases.

5 / 5

Workflow Clarity

A clear numbered sequence (Preamble → Steps 1–8) with real checkpoints: clarifying questions and interpretation choices gated on the user in step 1, an explicit spec-review gate with questions in step 6, and explicit skip/say-so rules for diagrams. Falls short of 5 because there is no explicit feedback loop for revising the spec if the user rejects it in step 6; above 3 because checkpoints are present and concrete, not just implied.

4 / 5

Progressive Disclosure

Good structure with clear sections (Preamble, Steps, Important), no buried or nested references, and content that mostly earns its inline place. Minor organization gaps keep it at 4: the ~55-line spec template and the dense handoff mechanics (step 8) are inlined in a 130-line file and could live in a references/ file; no bundle files exist to offload detail.

4 / 5

Total

16

/

20

Passed

Description

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

The description is concise, third-person, and action-oriented with four concrete capabilities, giving it good specificity and distinctiveness. Its main weaknesses are the complete absence of a 'Use when...' trigger clause and limited natural-keyword variations, which cap completeness and trigger-term quality at 3.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks to spec, plan, or design a new feature, or mentions writing a spec document or feature request."

Include natural user phrasings and synonyms such as "write a spec", "feature request", and "design doc" to improve trigger term coverage.

Mention the user-review checkpoint or handoff to planning to round out coverage of the skill's workflow.

DimensionReasoningScore

Specificity

"Spec a new feature — recall architecture knowledge, create a spec document, build an implementation plan, and break into tasks" lists four concrete third-person actions, matching the anchor for several specific actions with minor gaps (codebase exploration, user review, and handoff steps are omitted). Not 5 because coverage is not comprehensive; not 3 because it goes well beyond naming just 1–2 actions.

4 / 5

Completeness

The 'what' is clearly stated (four concrete actions) but there is no "Use when..." clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines. Not 4 because the 'when' is entirely absent rather than merely imprecise; not 2 because the 'what' is concrete, not vague.

3 / 5

Trigger Term Quality

Relevant keywords like "spec", "new feature", "spec document", and "implementation plan" are present, but common variations users naturally say — "write a spec", "feature request", "design doc", "plan a feature" — are missing. Fits the 'some relevant keywords but missing variations/synonyms' anchor rather than 4's fuller coverage.

3 / 5

Distinctiveness Conflict Risk

"Spec a new feature" with spec-document and implementation-plan language carves a distinct feature-planning niche with fairly specific triggers, though minor overlap risk exists with generic planning or architecture skills. Better than 3's 'could still overlap with similar skills', short of 5's fully minimal conflict risk.

4 / 5

Total

14

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 2 missing

Warning

Total

15

/

16

Passed

Repository

AndreJorgeLopes/devflow

Path

devflow-plugin/skills/spec-feature/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.