speckit-tasks

Generate an actionable, dependency-ordered tasks.md for the feature based on available design artifacts.

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/speckit-tasks/SKILL.md

Quality

Content

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is highly actionable and clearly sequenced, with concrete commands, exact paths, explicit validation steps, and worked checklist examples. The main weakness is conciseness, driven largely by the near-duplicate extension-hooks block repeated in two places.

Suggestions

Factor the duplicated extension-hooks handling (Pre-Execution Checks and step 6) into one shared block referenced by both call sites, noting only the hook key difference (before_tasks vs after_tasks).

Tighten or move the verbose hook output templates into a short reference, since they consume significant tokens for an optional path.

Consider extracting the detailed checklist format and phase structure into a referenced file if the skill grows, keeping SKILL.md as a lean overview.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and well-structured, but the extension-hooks handling block is repeated almost verbatim in 'Pre-Execution Checks' and again in step 6, and a few spots carry mild explanatory padding that could be tightened.	2 / 3
Actionability	Concrete commands ('check-prerequisites.ps1 -Json'), exact file paths, named templates, and worked checklist examples with explicit correct/wrong cases give fully executable, copy-paste-ready guidance.	3 / 3
Workflow Clarity	A clear numbered sequence with explicit validation checkpoints ('Validate task completeness', 'Format validation: Confirm ALL tasks follow the checklist format') and error-handling guidance for malformed hook YAML.	3 / 3
Progressive Disclosure	A single self-contained file with no bundle references; content is organized into well-labeled sections (Pre-Execution Checks, Outline, Task Generation Rules, Phase Structure), which is appropriate disclosure for a single-file skill.	3 / 3
	Total	11 / 12 Passed

Description

57%

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 clearly conveys the single concrete action and has a distinct niche, but it omits any explicit 'Use when' trigger guidance, leaving the when-to-use question unanswered. This is a solid, concise what-statement that would benefit from an explicit trigger clause.

Suggestions

Add a 'Use when...' clause naming natural trigger phrases, e.g. 'Use when the user asks to break a feature into development tasks, generate a task list, or plan implementation from spec-kit design artifacts.'

Broaden trigger-term coverage with user-facing phrasing such as 'task breakdown', 'implementation plan', or 'dependency-ordered task list' in addition to 'tasks.md'.

Consider listing two distinct actions (e.g. generate the tasks.md and produce a dependency graph) to move specificity to the top anchor.

Dimension	Reasoning	Score
Specificity	Names a concrete action ('Generate an actionable, dependency-ordered tasks.md for the feature') with qualifiers, but it is a single action rather than the multiple distinct concrete actions the top anchor requires.	2 / 3
Completeness	It states what the skill does, but the 'when to use it' guidance is entirely absent; per the guidelines a missing explicit trigger clause caps completeness at 2.	2 / 3
Trigger Term Quality	Terms like 'tasks.md' and 'design artifacts' are relevant but lean technical, with no 'Use when...' phrasing or common natural-language variations a user would actually say.	2 / 3
Distinctiveness Conflict Risk	Tied to a specific spec-kit workflow ('tasks.md for the feature based on available design artifacts'), giving it a clear niche unlikely to trigger for unrelated skills.	3 / 3
	Total	9 / 12 Passed

Validation

87%

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

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: unoplatform/uno
Path: .claude/skills/speckit-tasks/SKILL.md
Commit: 5927220

Reviewed: about 16 hours 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.