CtrlK
BlogDocsLog inGet started
Tessl Logo

writing-plans

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

58

Quality

66%

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 ./eval/local/skills/benchmarks/dependency/superpowers/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 strong, highly actionable planning skill with concrete templates, explicit validation checkpoints, and a self-review feedback loop. Its only mild weakness is a few rationale sentences that could be tightened for token efficiency.

DimensionReasoningScore

Conciseness

The body is lean and directive throughout, assuming Claude's competence, with only minor rationale sentences (e.g. "You reason best about code you can hold in context at once") that could be trimmed; it does not explain concepts Claude already knows.

4 / 5

Actionability

It provides copy-paste-ready plan and task templates with exact file paths, executable test/commit commands, expected output, and a 'No Placeholders' section enumerating concrete red flags — fully executable guidance covering the common cases.

5 / 5

Workflow Clarity

A clear sequenced process (Scope Check → File Structure → Task Right-Sizing → … → Self-Review → Execution Handoff) with an explicit Self-Review checklist (spec coverage, placeholder scan, type consistency) and a fix-and-retry feedback loop, plus per-task verification steps with expected PASS/FAIL output.

5 / 5

Progressive Disclosure

Sections are well-organized with clear headers and easy navigation; there is no bulky reference material that belongs in a separate bundle file, so the inline structure is appropriate, though the plan/task templates are sizeable.

4 / 5

Total

18

/

20

Passed

Description

43%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 but fails to state what the skill actually does, capping completeness and specificity. It reads as a pure 'when' clause with the 'what' omitted entirely.

Suggestions

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

Add concrete actions (plan decomposition, file-structure mapping, test-first task generation) so the 'what' is explicit, not just the 'when'.

Include a synonym like 'implementation plan' or 'design doc' alongside 'spec'/'requirements' to broaden natural trigger coverage.

DimensionReasoningScore

Specificity

The description names the domain ("spec or requirements for a multi-step task", "before touching code") but states no concrete capability — it never says the skill writes implementation plans, so it falls at the 'names the domain but actions are minimal' anchor rather than the entirely-vague 1.

2 / 5

Completeness

It provides a clear 'when' ("Use when you have a spec or requirements for a multi-step task, before touching code") but no 'what' — it never describes what the skill does, matching the 'only when is present without what' anchor.

2 / 5

Trigger Term Quality

"spec", "requirements", "multi-step task", and "before touching code" are natural phrases a user would say when needing this skill, giving good keyword coverage with only minor synonyms missing.

4 / 5

Distinctiveness Conflict Risk

The 'before touching code' timing clause carves a planning niche, but "spec", "requirements", and "multi-step task" are broad enough to overlap with brainstorming and other development-process skills.

3 / 5

Total

11

/

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