CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

speckit-tasks

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

Quality

64%

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 ./apps/reference/.claude/skills/speckit-tasks/SKILL.md

The canonical home for this skill is speckit-tasks in RihardsJ/software-factory

SKILL.md
Quality
Evals
Security

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 strongly actionable — exact commands, a strict per-task format with correct/incorrect examples, and a well-sequenced workflow ending in a validation checklist. Its weaknesses are the near-verbatim duplication of the extension-hook protocol across the pre- and post-execution sections and the absence of any bundle/reference structure, both fixable by extracting the hook rules into a shared reference file.

Suggestions

Extract the duplicated extension-hook protocol (enabled filtering, condition handling, dot-to-hyphen conversion, YAML error reporting, output templates) into a shared reference file (e.g. references/hooks.md) and have both Pre-Execution and Post-Execution sections point to it, removing ~30 duplicated lines.

Add a fallback for missing required inputs: state what to do if plan.md or spec.md is absent under FEATURE_DIR or if setup-tasks.sh fails or emits no FEATURE_DIR.

Show the expected shape of TASKS_TEMPLATE_CONTENT (or point to the template file) so the 'Generate tasks.md' step is copy-paste executable rather than dependent on unseen content.

DimensionReasoningScore

Conciseness

The body is dense and operational with no padding over concepts Claude already knows, but the extension-hook protocol (enabled filtering, condition handling, dot-to-hyphen replacement, YAML parse-error handling, output templates) is repeated nearly verbatim in both "Pre-Execution Checks" and "Mandatory Post-Execution Hooks" — roughly 30 duplicated lines that could be collapsed to a single shared rule. That is more than the 'minor instances' of a 4, but far from the padded over-explanation of a 2.

3 / 5

Actionability

Guidance is highly executable: the exact command ".specify/scripts/bash/setup-tasks.sh --json" with parsed JSON fields, a strict checklist format "- [ ] [TaskID] [P?] [Story?] Description with file path" with concrete correct and wrong examples, and shell escape syntax for quotes. Not 5 because hook invocation remains partly abstract ("the invocation may differ from the literal {command} id") and template filling depends on TASKS_TEMPLATE_CONTENT whose shape is not shown.

4 / 5

Workflow Clarity

Clear sequence: pre-execution hooks → setup script → load documents → task generation rules → generate tasks.md → post-execution hooks → completion report, ending in a "Done When" checklist. Validation checkpoints exist ("Validate task completeness", "Format validation: Confirm ALL tasks follow the checklist format") plus YAML-error feedback handling. Not 5 because there are minor gaps: no fallback if a required plan.md or spec.md is missing, and no handling if the setup script itself fails.

4 / 5

Progressive Disclosure

No bundle files exist (no references/, scripts/, or assets/), so everything lives inline in a ~200-line SKILL.md. Section structure is good, but the ~60 lines of hook-dispatch machinery — duplicated across two sections — clearly belongs in a shared reference file, matching "content that should be separate is inline". It is better organized than a monolithic wall of text (2), but not the well-split structure of a 4.

3 / 5

Total

14

/

20

Passed

Description

50%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 has a clear, concrete 'what' — generating a dependency-ordered tasks.md from design artifacts — but entirely lacks 'when to use it' trigger guidance and natural synonyms, which caps both completeness and trigger quality at 3. Adding a 'Use when...' clause naming spec-kit workflows and task-breakdown phrasings would lift most dimensions to 4-5.

Suggestions

Add an explicit trigger clause, e.g. "Use when working in a spec-kit project to break an approved spec/plan into implementation tasks, or when the user asks for a task list, task breakdown, or tasks.md for a feature."

Enumerate 1-2 more concrete actions to raise specificity, e.g. "...tasks.md with per-story phases, dependency graph, and parallel-execution examples".

Mention the spec-kit/.specify context (or tasks.md, spec.md, plan.md by name) in the description itself so generic planning requests don't collide with other task-management skills.

DimensionReasoningScore

Specificity

"Generate an actionable, dependency-ordered tasks.md" names the domain and one concrete action (produce a tasks.md output), and "based on available design artifacts" names the input, but coverage stops there. It matches the anchor 'Names domain and 1-2 concrete actions, but not comprehensive' — not 4 because it lists only a single action rather than several (the body's dependency graph, phase organization, and validation work is invisible here).

3 / 5

Completeness

The 'what' is clear ("Generate an actionable, dependency-ordered tasks.md for the feature based on available design artifacts") but there is no 'Use when...' clause or equivalent trigger guidance, so completeness is capped at 3 per the judging guidelines. Not 4 because the 'when' is entirely absent, not merely implicit-but-stated.

3 / 5

Trigger Term Quality

Relevant keywords are present ("tasks.md", "task generation" implied by "Generate", "feature", "design artifacts") but common natural variations users would say — "task breakdown", "task list", "implementation plan", "spec-kit" — are missing. This fits 'Some relevant keywords but missing common variations or synonyms' rather than 4's 'a few natural terms missing' because the majority of natural phrasings are absent.

3 / 5

Distinctiveness Conflict Risk

"tasks.md" and "design artifacts" point at a spec-kit-style niche, giving some distinctiveness, but the description never mentions spec-kit, .specify, or the spec-driven workflow, so generic requests to break a feature into tasks could overlap with sibling planning skills. This fits 'Somewhat specific but could still overlap with similar skills' — more anchored than a 2, but without the near-elimination of overlap that a 4 requires.

3 / 5

Total

12

/

20

Passed

Validation

87%

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

CriteriaDescriptionResult

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

RihardsJ/software-factory

Path

apps/reference/.claude/skills/speckit-tasks/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.