planning-and-task-breakdown

Breaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible.

Quality

80%

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 ./skills/planning-and-task-breakdown/SKILL.md

Quality

Content

81%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 delivers a clear, actionable planning workflow with explicit checkpoints and validation, structured efficiently without padding. Progressive disclosure is solid, with only minor organization gains available from splitting the templates into separate files.

Dimension	Reasoning	Score
Conciseness	The body is well-organized with no concept-explaining fluff, but sections like the Common Rationalizations table and some prose could be trimmed, fitting the "efficient with minor over-explanation" anchor.	4 / 5
Actionability	Concrete templates, specific file paths (tasks/plan.md, tasks/todo.md), and tracker commands (bd dep add) give mostly executable guidance, with a few abstract spots like "estimate scope" leaving minor gaps.	4 / 5
Workflow Clarity	A clear five-step sequence carries explicit checkpoints (Step 5), a verification checklist, and feedback guidance ("stop and ask" before overwriting incomplete plans), matching the anchor for explicit validation and feedback loops.	5 / 5
Progressive Disclosure	A single well-structured SKILL.md with one clearly signaled one-level reference (definition-of-done.md) and no nested bundle files is good, though the inline templates could be split out for cleaner navigation.	4 / 5
	Total	17 / 20 Passed

Description

78%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 answers both what the skill does and when to use it, with strong, natural trigger phrasing. It is somewhat light on enumerating multiple concrete capabilities and has minor overlap risk with adjacent planning skills.

Dimension	Reasoning	Score
Specificity	Names the domain and one concrete action ("Breaks work into ordered tasks", "break work into implementable tasks") but does not list several specific capabilities, matching the anchor for 1-2 concrete actions without comprehensive coverage.	3 / 5
Completeness	A clear "what" ("Breaks work into ordered tasks") is paired with multiple explicit "Use when…" clauses containing concrete trigger phrases, fully answering both what and when.	5 / 5
Trigger Term Quality	Natural trigger phrases like "task feels too large to start", "estimate scope", and "parallel work is possible" give good keyword coverage, though a few common synonyms are missing.	4 / 5
Distinctiveness Conflict Risk	The task-decomposition niche is mostly distinct with specific triggers, but terms like "estimate scope" carry minor overlap risk with general project-management skills.	4 / 5
	Total	16 / 20 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: addyosmani/agent-skills
Path: skills/planning-and-task-breakdown/SKILL.md
Commit: 48cb116

Reviewed: ~18 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.