writing-plans

Use when you have a spec or requirements for a multi-step task, before touching code

3.58x

Quality

64%

Does it follow best practices?

Impact

86%

3.58x

Average score across 8 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./bundled/skills/writing-plans/SKILL.md

Quality

Content

88%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 a strong, highly actionable planning skill: complete templates, an explicit TDD validation loop, and clear sectioning. The only minor weakness is slight redundancy between the Overview and Remember sections.

Dimension	Reasoning	Score
Conciseness	The body is lean and largely assumes Claude's competence, with only minor redundancy such as restating 'DRY. YAGNI. TDD. Frequent commits' in the Overview and again in the Remember section.	4 / 5
Actionability	It provides fully worked, copy-paste-ready templates with exact file paths, runnable code, exact commands (pytest/git), and expected output, covering the common task structure comprehensively.	5 / 5
Workflow Clarity	The TDD task structure has an explicit, sequenced validation loop — write failing test, verify FAIL, implement, verify PASS, commit — with expected outputs as feedback checkpoints.	5 / 5
Progressive Disclosure	No bundle files exist, but the body is well-organized into clearly signaled sections (Overview, Granularity, Header, Task Structure, Remember, Execution Handoff); the inlined templates are reasonably placed, with only minor organization gaps.	4 / 5
	Total	18 / 20 Passed

Description

40%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 is an effective trigger clause but functionally incomplete: it tells Claude when to fire without saying what the skill does. Adding the 'what' (write implementation plans / break work into bite-sized TDD tasks) would lift both completeness and specificity.

Suggestions

Lead with the 'what' before the 'when', e.g. 'Write comprehensive implementation plans that break multi-step tasks into bite-sized TDD tasks. Use when you have a spec or requirements for a multi-step task, before touching code.'

Add natural synonyms users say when planning — 'plan', 'implementation plan', 'break down work', 'estimate' — to broaden trigger coverage.

Name the concrete outputs ('plan document with exact file paths, code, and test commands') so the skill is distinguishable from generic planning or brainstorming skills.

Dimension	Reasoning	Score
Specificity	The description names the domain ('spec or requirements for a multi-step task') but states no concrete actions the skill performs — it never says it writes plans or breaks tasks into steps, matching the 'names the domain but actions are minimal or generic' anchor.	2 / 5
Completeness	It provides a clear explicit 'when' ('Use when... before touching code') but the 'what' is entirely missing — the skill never states it produces an implementation plan, matching the anchor 'only "when" is present without "what"'.	2 / 5
Trigger Term Quality	'spec', 'requirements', and 'multi-step task' are natural terms, but common synonyms users actually say ('plan', 'implementation plan', 'break down', 'estimate') are absent, so keyword coverage is only partial.	3 / 5
Distinctiveness Conflict Risk	The 'before touching code' planning niche is mostly distinct, with only minor overlap risk against closely related sibling skills (brainstorming, executing-plans) referenced in the body.	4 / 5
	Total	11 / 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: foryourhealth111-pixel/Vibe-Skills
Path: bundled/skills/writing-plans/SKILL.md
Commit: d5ae560

Reviewed: 1 day 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.