speckit-tasks

Break down implementation plans into actionable task lists. Use after planning to create a structured task breakdown. Generates tasks.md with ordered, dependency-aware tasks.

Quality

75%

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 ./bundled/skills/speckit-tasks/SKILL.md

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 highly actionable with concrete paths, an exact task format, and correct/incorrect examples, plus a clear sequenced workflow with validation checkpoints. Its weaknesses are mild redundancy between the Outline and the dedicated rules sections, and the absence of an explicit error-recovery feedback loop or external reference files for the detail-heavy rules.

Suggestions

De-duplicate the phase/task-organization content that currently appears in both the Outline (steps 3-4) and the Task Generation Rules / Phase Structure sections; reference one from the other to tighten the body.

Add an explicit fix-and-retry feedback loop to the validation steps (e.g., 'if format validation fails, list the offending tasks, fix them, and re-validate before reporting').

Consider moving the full Checklist Format spec and Task Organization rules into a referenced file (e.g. references/task-format.md) so SKILL.md stays a lean overview pointing one level deep to the detail.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and task-relevant but repeats material across sections — phase structure and task organization appear in both the Outline (steps 3-4) and the dedicated Task Generation Rules / Phase Structure sections — which is more than minor trimming.	3 / 5
Actionability	Provides fully executable, copy-paste-ready guidance: exact script and template paths, a strict checklist format string, and multiple correct/incorrect examples with concrete file paths covering the common cases.	5 / 5
Workflow Clarity	A clear five-step sequence with explicit validation checkpoints ('Validate task completeness', 'Confirm ALL tasks follow the checklist format'), but it lacks an explicit fix-and-retry feedback loop for validation failures, keeping it below 5.	4 / 5
Progressive Disclosure	Well-organized into clear sections with headers, but at ~127 lines the detailed checklist-format spec and organization rules are inlined rather than split into separate reference files (none exist), so it is good but not the clean overview-with-one-level-references of 5.	4 / 5
	Total	16 / 20 Passed

Description

75%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 strong and well-balanced, clearly stating what the skill does and when to use it with concrete actions and natural trigger terms. Its main limitation is that the 'when' clause names a workflow stage rather than concrete user-facing trigger phrases, and the spec-kit niche that would maximize distinctiveness is not surfaced in the description text.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions ('Break down implementation plans into actionable task lists', 'create a structured task breakdown', 'Generates tasks.md with ordered, dependency-aware tasks') with only minor coverage gaps, fitting the 'several specific actions' anchor rather than the comprehensive 5.	4 / 5
Completeness	Answers both 'what' (break down plans, generate tasks.md) and 'when' ('Use after planning'), but the 'when' is a workflow position rather than concrete user-facing trigger phrases, keeping it below the explicit-trigger anchor of 5.	4 / 5
Trigger Term Quality	Includes reasonably natural terms ('implementation plans', 'task lists', 'planning', 'task breakdown') a user might say, but misses common synonyms like 'todo list', 'backlog', or 'break this spec into tasks', so it is good but not comprehensive.	4 / 5
Distinctiveness Conflict Risk	Targets a fairly distinct niche (spec-kit task breakdown producing tasks.md) with minor overlap risk against generic planning skills; the description does not surface the spec-kit trigger that would make it clearly distinct at 5.	4 / 5
	Total	16 / 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
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: foryourhealth111-pixel/Vibe-Skills
Path: bundled/skills/speckit-tasks/SKILL.md
Commit: ddcaa2a

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