writing-plans

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

Quality

64%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

tessl review fix ./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 highly actionable and well-sequenced, with concrete copy-paste templates and explicit TDD validation checkpoints throughout. Its main weakness is the frontmatter description's missing 'what', which is reflected at the description-judge level rather than here.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean templates and concrete guidance with only minor over-explanation (e.g. the 'Document everything they need to know' prose and 'DRY. YAGNI. TDD.' line), fitting 'efficient; minor instances of over-explanation that could be trimmed'.	4 / 5
Actionability	It provides fully copy-paste-ready task-structure templates with exact file paths, executable test/commit commands, expected outputs, and a complete plan-document header, matching 'fully executable; copy-paste ready code or commands'.	5 / 5
Workflow Clarity	The bite-sized TDD cycle is explicitly sequenced (write failing test -> verify it fails -> implement -> verify it passes -> commit) with built-in validation checkpoints and feedback loops, matching 'clear sequence with explicit validation steps; feedback loops for error recovery'.	5 / 5
Progressive Disclosure	As a single-file skill with no bundle files, it is well-organized into clear sections and references sub-skills via @-syntax, but the inline plan-header and task-structure templates could arguably live in reference files, fitting 'good structure; most content appropriately placed; 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 has an explicit and reasonably natural trigger clause but is missing the 'what' entirely — it never states that the skill writes implementation plans. This absence of concrete actions caps both specificity and completeness low.

Suggestions

Lead with the concrete action, e.g. 'Writes comprehensive, bite-sized implementation plans from a spec or requirements. Use when you have a spec or requirements for a multi-step task, before touching code.'

Add natural synonyms such as 'plan', 'implementation plan', and 'break down' to broaden trigger coverage.

State the deliverable explicitly (a plan saved to docs/plans/) so the 'what' is unambiguous and distinctiveness is sharper.

Dimension	Reasoning	Score
Specificity	The description names the domain ('spec or requirements for a multi-step task') and implies planning 'before touching code', but states no concrete actions — it never says it writes or produces a plan, matching the 'names the domain but actions are minimal or generic' anchor.	2 / 5
Completeness	The 'when' is explicit ('Use when you have a spec or requirements for a multi-step task, before touching code'), but the 'what' is entirely absent — it never describes what the skill produces, matching the 'only when is present without what' anchor.	2 / 5
Trigger Term Quality	Terms like 'spec', 'requirements', 'multi-step task' are reasonably natural, but coverage is limited with common variations ('plan', 'implementation plan', 'break down a task') missing, fitting 'some relevant keywords but missing common variations or synonyms'.	3 / 5
Distinctiveness Conflict Risk	The 'spec/requirements before touching code' trigger carves a mostly-distinct planning niche with only minor overlap risk against related brainstorming or execution skills, fitting 'mostly distinct; minor overlap risk'.	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: roman01la/skills-agents
Path: skills/writing-plans/SKILL.md
Commit: aa6f9d3

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