CtrlK
BlogDocsLog inGet started
Tessl Logo

writing-plans

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

66

Quality

79%

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 ./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.

A highly actionable, well-sequenced instruction skill with copy-paste templates, explicit validation loops, and a self-review checklist; its only weaknesses are mild Overview padding and inlined templates that could be externalized.

DimensionReasoningScore

Conciseness

The body is largely lean and directive ('DRY. YAGNI. TDD. Frequent commits.', 'Exact file paths always'), with only minor padding — the chatty Overview voice and the Self-Review section re-listing the No-Placeholder patterns could be trimmed.

4 / 5

Actionability

Provides copy-paste-ready templates with exact file paths, runnable commands (pytest ...::test_name -v), expected outputs, complete code blocks, and a concrete anti-placeholder list — covering the common task lifecycle fully.

5 / 5

Workflow Clarity

Clear end-to-end sequence (Scope Check through Execution Handoff) with explicit validation checkpoints — the TDD red-then-green loop and the 3-point Self-Review checklist supply feedback loops for error recovery.

5 / 5

Progressive Disclosure

Well-organized into clearly labeled one-level sections with no nested references, but large inline template blocks (Plan Document Header, Task Structure) are inlined and no bundle files exist to split out detailed material.

4 / 5

Total

18

/

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 has a clear, explicit trigger clause with natural keywords and a distinct niche, but it underspecifies the 'what' — the actual capability (writing implementation plans) is implied by the skill name rather than stated in the description.

Suggestions

Add an explicit 'what' clause naming the concrete action, e.g. 'Writes comprehensive implementation plans from a spec or requirements'.

Expand trigger terms with synonyms users commonly say, such as 'plan', 'implementation plan', or 'break down a task'.

Mention the output artifact (a saved plan document) to sharpen the 'what' and reduce overlap with brainstorming/executing skills.

DimensionReasoningScore

Specificity

Names the domain ('spec or requirements for a multi-step task') and trigger condition ('before touching code') but does not enumerate the concrete actions the skill performs (writing plans, task decomposition), leaving the 'what' only implied.

3 / 5

Completeness

The 'when' is explicitly stated with a concrete 'Use when...' trigger, but the 'what' (creates implementation plans) is only weakly implied rather than stated, keeping it below a 5.

4 / 5

Trigger Term Quality

Includes several natural terms a user would say ('spec', 'requirements', 'multi-step task', 'before touching code') but misses common synonyms like 'plan', 'implementation', or 'break down'.

4 / 5

Distinctiveness Conflict Risk

The 'spec/requirements for a multi-step task, before touching code' framing carves a fairly distinct niche with only minor overlap risk against adjacent planning skills like brainstorming or executing-plans.

4 / 5

Total

15

/

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
lucianghinda/superpowers-ruby
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.