planner

Create structured plans for multi-task projects that can be used by the task-orchestrator skill. Use when breaking down complex work into parallel and sequential tasks with dependencies.

Quality

80%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Fix and improve this skill with Tessl

tessl review fix ./skills/planner/SKILL.md

Quality

Content

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, highly actionable planning skill with a clear phased workflow, review checkpoint, and copy-paste plan template. Its only weakness is minor redundancy and non-essential provenance notes that keep conciseness at the mid anchor.

Suggestions

Consolidate the save-file rule to a single authoritative statement (e.g., Safety Boundaries only) and remove the duplicate in Quick Start Phase 4 to tighten the body.

Drop or move the "Source: Adapted from..." / "Adapted from am-will's..." provenance lines out of the executable content, since they consume tokens without aiding task execution.

Dimension	Reasoning	Score
Conciseness	The body is largely lean and assumes Claude's competence (no explanations of basic concepts), but the save-file rule is restated three times (frontmatter permissions, Quick Start Phase 4, Safety Boundaries) and provenance notes ("Source: Adapted from...", "Adapted from am-will's...") add tokens that don't aid execution, placing it at the mostly-efficient-could-be-tightened anchor.	2 / 3
Actionability	As an instruction-only skill it provides concrete, copy-paste-ready guidance: a full plan template with specific fields (Location, Perceived Complexity 1-10, Dependencies, Acceptance Criteria, Validation), a bad-vs-good task breakdown, and an exact hand-off command, matching the fully actionable top anchor.	3 / 3
Workflow Clarity	The multi-step process is clearly sequenced as Phases 0-4 with an explicit review checkpoint (Phase 3 subagent review) and per-sprint demo/verification checklists, satisfying the clear-sequence-with-validation anchor; it is not the 2 anchor because checkpoints are explicit rather than implicit.	3 / 3
Progressive Disclosure	No bundle files exist and the content is well-organized into clearly labeled sections (Quick Start, Key Principles, Plan Template, Hand-off, Safety Boundaries, Related) with no nested/deep references, so the well-organized-sections condition for a 3 applies.	3 / 3
	Total	11 / 12 Passed

Description

75%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A solid description that answers both what and when with an explicit trigger clause and a clearly scoped niche tied to a companion skill. It is slightly under-developed on action specificity and trigger-term breadth, which keep specificity and trigger_term_quality at the mid anchor.

Suggestions

Expand specificity by listing a few more concrete planning actions (e.g., "define sprint goals, map task dependencies, capture acceptance criteria") rather than one bundled action.

Broaden trigger terms with natural user phrasings such as "project plan", "work breakdown", or "task list with dependencies" to improve discovery.

Dimension	Reasoning	Score
Specificity	Names the domain and concrete actions ("Create structured plans for multi-task projects", "breaking down complex work into parallel and sequential tasks with dependencies"), but stops short of a comprehensive list of multiple distinct actions, so it sits at the named-but-not-comprehensive anchor rather than 3.	2 / 3
Completeness	It explicitly states both what it does ("Create structured plans for multi-task projects") and when to use it via an explicit "Use when breaking down complex work..." clause, satisfying the top anchor for both what and when.	3 / 3
Trigger Term Quality	Includes some natural phrasing a user might say ("breaking down complex work", "parallel and sequential tasks", "tasks with dependencies") but omits common variations like "project plan", "work breakdown", or "task list", matching the some-relevant-keywords anchor rather than full coverage.	2 / 3
Distinctiveness Conflict Risk	The explicit pairing with the task-orchestrator skill and the specific trigger of parallel/sequential tasks with dependencies carve a clear niche unlikely to fire for unrelated skills; it is more distinctive than the overlap-prone anchor at 2.	3 / 3
	Total	10 / 12 Passed

Validation

75%

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

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
metadata_field	'metadata' should map string keys to string values	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
relative_links	Relative link issues: 1 suspicious	Warning

	Total	12 / 16 Passed

Repository: jdrhyne/agent-skills
Commit: a4d31ad

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