skill-writing-plans

Create zero-context implementation plans with bite-sized tasks — use for multi-step feature planning

Quality

72%

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/skill-writing-plans/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, copy-paste-ready code and a well-sequenced TDD workflow supported by checklists. Its main weakness is verbosity from duplicating the template in a full example and the heavy compliance framing.

Suggestions

Collapse the template and the worked example into one: show the template once with a concrete example inline, or move the full email-validation example to a reference file.

Tighten the 'MANDATORY COMPLIANCE' section — the prohibition list and the repeated bottom-line restatement can be condensed without losing force.

Add an explicit error-recovery step to the task template (e.g., 'If the test fails to pass, fix the code and re-run; do not proceed until it passes').

Dimension	Reasoning	Score
Conciseness	Mostly efficient instructional content, but the full worked example largely duplicates the task template structure, and the 'MANDATORY COMPLIANCE' banner plus the bottom-line restatement add padding that could be trimmed.	3 / 5
Actionability	Fully executable guidance: exact file paths, complete TypeScript test and implementation code, exact npm/git commands, and expected output for every step, plus a complete email-validation worked example.	5 / 5
Workflow Clarity	The TDD cycle is clearly sequenced with explicit verify-fails and verify-passes checkpoints and a checklist, though the template lacks an explicit error-recovery feedback loop (what to do when a checkpoint fails).	4 / 5
Progressive Disclosure	Well-organized with clear section headers and no nested reference chains; the skill is self-contained with no bundle files, and content is appropriately placed, though a few sections (e.g., the full example) could optionally live in a reference file.	4 / 5
	Total	16 / 20 Passed

Description

70%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 states what the skill does and gives a usable trigger, but it is a single-action description rather than a comprehensive capability list. Stronger trigger phrasing and a second concrete action would lift it to the top band.

Suggestions

Add one or two more concrete actions (e.g., 'break features into 2-5 minute tasks, sequence TDD steps, and generate commit-ready task lists').

Make the trigger more explicit and user-voiced: 'Use when the user asks to plan a multi-step feature or break work into implementable tasks.'

Include common synonyms like 'task breakdown' or 'feature planning' to broaden natural keyword coverage.

Dimension	Reasoning	Score
Specificity	Names the domain ('implementation plans') and one concrete action ('Create ... with bite-sized tasks'), but offers only that single action rather than a list of specific capabilities.	3 / 5
Completeness	Provides a clear 'what' ('Create zero-context implementation plans with bite-sized tasks') and an explicit 'when' ('use for multi-step feature planning'), but the trigger could be more concrete.	4 / 5
Trigger Term Quality	'implementation plans' and 'multi-step feature planning' are natural phrases a user would say, though a few common synonyms (e.g., 'break down a feature', 'task breakdown') are missing.	4 / 5
Distinctiveness Conflict Risk	The 'zero-context implementation plans with bite-sized tasks' niche is fairly distinct, with only minor overlap risk against other planning-related skills.	4 / 5
	Total	15 / 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: nyldn/claude-octopus
Path: skills/skill-writing-plans/SKILL.md
Commit: 242e51d

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.