speckit-tasks

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

Quality

58%

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

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 content is a well-sequenced, actionable workflow with concrete commands, paths, and a strict output format, including validation steps in the report. Its main weaknesses are duplicated hook-handling instructions hurting conciseness and the absence of any bundle/reference files for the detailed rules.

Suggestions

Factor the near-identical before_tasks/after_tasks hook-handling blocks into a single shared reference (e.g. references/hooks.md) and link to it from both sites to remove the duplication.

Move the detailed Task Generation Rules and Phase Structure into references/task-rules.md, leaving a concise overview plus a one-level-deep pointer in SKILL.md.

Add a validate->fix->retry feedback loop (e.g. regenerate tasks if format validation fails) to lift workflow clarity toward 5.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient procedural guidance, but the extension-hooks handling is duplicated almost verbatim in Pre-Execution Checks and step 6, and several explanatory asides could be trimmed; it is not a 4 because the repeated hook blocks are clear redundancy, yet not a 2 since most content earns its place.	3 / 5
Actionability	Concrete commands (check-prerequisites.ps1 -Json), exact file paths (.specify/templates/tasks-template.md, plan.md, spec.md), and a strict checklist format with correct/wrong examples give mostly executable guidance; not a 5 because entity/contract-to-story mapping and JSON parsing remain described rather than specified.	4 / 5
Workflow Clarity	A clearly numbered 6-step outline with explicit validation checkpoints ('Validate task completeness', 'Format validation: Confirm ALL tasks follow the checklist format') and graceful hook fallbacks; not a 5 because there is no validate->fix->retry feedback loop for the generation itself, only a final report.	4 / 5
Progressive Disclosure	Sections are organized (Outline, Task Generation Rules, Phase Structure) but no bundle files exist and ~190 lines of detailed rules plus the duplicated hook-handling blocks are fully inlined rather than split into one-level-deep references; the under-50-line exception does not apply, so it stays at 3 rather than 4.	3 / 5
	Total	14 / 20 Passed

Description

53%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 clearly states what the skill produces but omits any explicit trigger ('Use when...') guidance, which limits completeness and trigger-term quality. It is reasonably distinctive within the spec-kit niche.

Suggestions

Add a 'Use when...' clause naming concrete triggers, e.g. 'Use when generating a task breakdown for a spec-kit feature from plan.md/spec.md, or when the user asks to turn design artifacts into an actionable task list.'

Broaden trigger terms with natural synonyms ('task list', 'task breakdown', 'work breakdown') alongside 'tasks.md' and 'design artifacts'.

List the concrete sub-actions (e.g. extract user stories, map data models/contracts, emit dependency graph) to lift specificity from one action to several.

Dimension	Reasoning	Score
Specificity	Names a concrete output ('dependency-ordered tasks.md ... based on available design artifacts') but describes essentially one generation action rather than a list of several specific actions, fitting the '1-2 concrete actions' anchor; not a 4 because no multi-action coverage is given.	3 / 5
Completeness	The 'what' is clear (generate a dependency-ordered tasks.md from design artifacts) but there is no 'Use when...' or equivalent trigger guidance, which per the rubric caps completeness at 3; not a 4 because the 'when' is entirely absent rather than merely weak.	3 / 5
Trigger Term Quality	Terms like 'tasks.md', 'dependency-ordered', and 'design artifacts' are relevant but lean technical/jargon; common natural variations a user would say ('task list', 'break down the feature into tasks') are missing, so it sits at the 'some relevant keywords' anchor rather than 4.	3 / 5
Distinctiveness Conflict Risk	Tied to a specific spec-kit niche (tasks.md from design artifacts) it is mostly distinct with only minor overlap risk against generic planning skills; not a 5 because the phrasing is not niche-specific enough to eliminate overlap with general task-planning skills.	4 / 5
	Total	13 / 20 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: eaa505e

Reviewed: 3 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.