CtrlK
BlogDocsLog inGet started
Tessl Logo

writing-plans

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

55

Quality

61%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./doc/skills/writing-plans/SKILL.md
SKILL.md
Quality
Evals
Security

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 body is a high-quality, concrete planning skill: fully executable templates, a clear sequenced workflow, and a built-in self-review validation loop. Its only weak spot is progressive disclosure — everything lives in one ~170-line file with no external references — though it is well sectioned.

DimensionReasoningScore

Conciseness

The body is lean and directive throughout — it avoids explaining concepts Claude already knows and every section earns its tokens — though a few narrative passages (e.g. 'You reason best about code you can hold in context at once...') could be trimmed, fitting 'efficient; minor instances of over-explanation'.

4 / 5

Actionability

It provides copy-paste-ready templates (plan header, task structure with real file paths, exact pytest/git commands, inline test and implementation code) covering the common cases, matching 'fully executable; copy-paste ready code or commands'.

5 / 5

Workflow Clarity

The process is clearly sequenced (Scope Check → File Structure → Task Right-Sizing → Task Structure → No Placeholders → Self-Review → Execution Handoff) with an explicit Self-Review validation checklist and a spec-coverage/placeholder/type-consistency feedback loop, matching 'clear sequence with explicit validation steps; checklists'.

5 / 5

Progressive Disclosure

No bundle files exist, yet the single SKILL.md is well-organized into focused sections with clear headers and the plan/task templates are integral rather than referenceable; this is good structure with minor organization gaps rather than the ideal one-level-deep reference split, fitting 'good structure; most content appropriately placed'.

4 / 5

Total

18

/

20

Passed

Description

35%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 functions well as a trigger (clear 'when') but fails to state what the skill does, listing no concrete actions and omitting the core 'writes implementation plans' capability. It is distinct enough to avoid most conflicts but is incomplete and unspecific.

Suggestions

Lead with a 'what' clause naming the concrete action, e.g. 'Write comprehensive, bite-sized implementation plans from a spec or requirements, before touching code'.

Add natural synonyms users would say — 'implementation plan', 'break down a spec', 'task decomposition' — to broaden trigger coverage.

Mention key deliverables (file-structure map, TDD task steps, self-review checklist) so the capability is concrete rather than implied.

DimensionReasoningScore

Specificity

The description ('Use when you have a spec or requirements for a multi-step task, before touching code') lists no concrete actions at all — it is purely a trigger with no verb describing what the skill does, matching the 'entirely vague; no concrete actions' anchor.

1 / 5

Completeness

It has a clear 'when' ('Use when you have a spec...') but no 'what' — it never states that the skill writes implementation plans, matching 'only when is present without what'; not a 3 because the what is absent rather than merely weakly implied.

2 / 5

Trigger Term Quality

It includes relevant natural terms ('spec', 'requirements', 'multi-step task', 'before touching code') but misses common synonyms a user might say ('plan', 'implementation plan', 'break down', 'task list'), fitting 'some relevant keywords but missing common variations'.

3 / 5

Distinctiveness Conflict Risk

The trigger carves a fairly distinct planning-from-spec niche ('spec or requirements for a multi-step task, before touching code') with only minor overlap risk against related brainstorming/executing skills, fitting 'mostly distinct; minor overlap risk'.

4 / 5

Total

10

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
jacklandrin/OnlySwitch
Reviewed

Table of Contents

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.