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

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

77%

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 with concrete templates, a sizing table, and well-sequenced validation checkpoints, making it strong on actionability and workflow clarity. It loses points on conciseness for over-explaining concepts Claude already knows, and on progressive disclosure for being a monolithic file that cites a missing reference.

Suggestions

Trim conceptual framing like the Overview and 'Common Rationalizations' table to respect token budget; Claude already understands why planning matters.

Resolve the dangling reference: either create references/definition-of-done.md or remove the pointer in 'See Also' to a file not in the bundle.

Dimension	Reasoning	Score
Conciseness	The body is well-structured but runs long for a planning skill, with explanatory prose Claude largely already knows (e.g. 'Good task breakdown is the difference between...') and a 'Common Rationalizations' section that could be trimmed.	2 / 3
Actionability	Provides copy-paste-ready task and plan templates, a concrete sizing table, explicit file output paths (tasks/plan.md, tasks/todo.md), and specific checkpoint checklists.	3 / 3
Workflow Clarity	Five clearly sequenced steps with explicit validation checkpoints ('Checkpoint: After Tasks 1-3') and a final verification checklist, satisfying the feedback-loop requirement.	3 / 3
Progressive Disclosure	The body is a single monolithic file; no bundle files exist in references/, scripts/, or assets/, yet it references references/definition-of-done.md in 'See Also' that is not present in the bundle.	2 / 3
	Total	10 / 12 Passed

Description

77%

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 answers both what and when with concrete actions and explicit triggers, giving it strong completeness and specificity. Trigger term breadth and distinctiveness are the weaker areas, as it leans on a single phrasing and overlaps with general planning skills.

Suggestions

Add more natural trigger phrases users would actually say, e.g. 'plan', 'decompose', 'todo list', or 'scope estimation'.

Sharpen distinctiveness by framing the niche more narrowly, e.g. emphasizing 'implementable, dependency-ordered engineering tasks' to avoid overlap with generic planning skills.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions: 'Breaks work into ordered tasks' and decomposes work into 'small, verifiable tasks with explicit acceptance criteria', matching the multi-action anchor.	3 / 3
Completeness	Explicitly answers what ('Breaks work into ordered tasks') and when via two distinct 'Use when...' clauses with explicit triggers.	3 / 3
Trigger Term Quality	Includes relevant natural phrases ('spec or clear requirements', 'estimate scope', 'parallel work') but omits common variations users might say such as 'plan', 'decompose', or 'todo list'.	2 / 3
Distinctiveness Conflict Risk	The task-breakdown niche is reasonably specific, but 'break work into tasks' overlaps with generic planning skills and could trigger for adjacent skills like project management.	2 / 3
	Total	10 / 12 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
referenced_paths_exist	Referenced path issues: 1 missing	Warning

	Total	15 / 16 Passed

Repository: addyosmani/agent-skills
Commit: 70b7506

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.