Name: spec-feature
Rating: 56.8 (1 reviews)
Author: AndreJorgeLopes

spec-feature

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

Quality

71%

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

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

Quality

Content

63%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 well-sequenced, largely actionable planning workflow with concrete commands and a thorough spec template. Its main weaknesses are verbosity in the handoff step, the absence of an explicit spec-validation checkpoint, and a monolithic structure with no progressive references.

Suggestions

Tighten step 8's handoff paragraph to the essential invocation and boundary rule, moving spawn_task/worktree internals to a reference if needed.

Add an explicit validation checkpoint (e.g. 'Review the spec against the acceptance criteria before handoff').

Extract the spec document template into a referenced file (e.g. references/spec-template.md) to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	Mostly efficient process prose, but step 8's handoff paragraph over-explains spawn_task/worktree mechanics and the diagram preamble is padded; these could be tightened without losing clarity.	3 / 5
Actionability	Provides concrete, executable guidance (git branch regex, mark_chapter call args, terminal-title bash snippet, full spec template, handoff invocation), though Hindsight recall/retain tool calls lack exact argument syntax.	4 / 5
Workflow Clarity	Clear numbered sequence (Preamble + 8 steps) with a user-review checkpoint (step 6) and AskUserQuestion gate, but there is no explicit 'validate the spec' step before handoff, leaving a minor checkpoint gap.	4 / 5
Progressive Disclosure	Good section structure, but the skill is a >50-line monolith with a large inline spec template and no reference files at all; the template and diagram guidance are content that could live in a separate reference file.	3 / 5
	Total	14 / 20 Passed

Description

66%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 third-person, specific, and lists multiple concrete actions, but it lacks an explicit 'when to use' trigger clause and omits major skill components (diagrams, handoff). Adding a 'Use when...' clause would raise completeness and trigger quality.

Suggestions

Add an explicit 'Use when...' clause naming natural triggers (e.g. 'Use when speccing a new feature, before writing code').

Mention the diagram and handoff outputs so the action list fully covers what the skill does.

Include common synonyms ('design doc', 'RFC', 'feature plan') to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions ('recall architecture knowledge, create a spec document, build an implementation plan, and break into tasks') but omits significant parts of the skill (diagram generation, phase handoff), so coverage has minor gaps rather than being comprehensive.	4 / 5
Completeness	The 'what' is clear (recall, spec, plan, tasks) but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines.	3 / 5
Trigger Term Quality	Natural terms like 'spec a new feature', 'spec document', 'implementation plan', and 'tasks' are present and would be said by users, though synonyms like 'design doc', 'RFC', or 'planning' are missing.	4 / 5
Distinctiveness Conflict Risk	The spec/planning niche is mostly distinct, but there is minor overlap risk with closely related planning skills (the skill itself references writing-plans and the plan phase).	4 / 5
	Total	15 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 2 missing	Warning

	Total	15 / 16 Passed

Repository: AndreJorgeLopes/devflow
Path: devflow-plugin/skills/spec-feature/SKILL.md
Commit: bd4b70c

Reviewed: 13 days 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.