CtrlK
BlogDocsLog inGet started
Tessl Logo

writing-plans

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

56

Quality

64%

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.

The skill body is a strong, actionable planning template with concrete examples, a self-review validation checklist, and clear sequencing. The only soft spot is progressive disclosure: it is a self-contained single file with no referenced sub-materials to navigate.

DimensionReasoningScore

Conciseness

The body is dense and instructive ("DRY. YAGNI. TDD. Frequent commits.", compact templates) with only minor over-explanation such as the "You reason best about code you can hold in context" framing, fitting the efficient-with-trimmable-excess anchor.

4 / 5

Actionability

It provides copy-paste-ready plan header and task-structure templates with exact file paths, executable test/commit commands, and concrete code blocks covering the common task pattern, matching the fully-executable anchor.

5 / 5

Workflow Clarity

The process is clearly sequenced (Scope Check → File Structure → Task Structure → Self-Review → Execution Handoff) with an explicit Self-Review checklist (spec coverage, placeholder scan, type consistency) and a fix-and-move-on feedback loop, matching the explicit-validation-and-checklist anchor.

5 / 5

Progressive Disclosure

No bundle files exist, so all content is inline in well-organized sections with clear headers; structure is good and navigation is easy, though the header/task templates could arguably live in separate reference files, placing this just below the ideal one-level-deep reference anchor.

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 a strong, explicit trigger but fails to state what the skill does, leaning on the skill name for the "what". Adding a concrete action clause would lift completeness and specificity materially.

Suggestions

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

Add a couple of natural synonyms such as "implementation plan", "task breakdown", or "spec-to-plan" to broaden trigger coverage.

State the "what" explicitly in the description text rather than relying on the skill name.

DimensionReasoningScore

Specificity

The description gives only a trigger ("Use when you have a spec or requirements for a multi-step task, before touching code") and never states the action; the "what" is implied solely by the skill name, matching the anchor for naming the domain with minimal actions.

2 / 5

Completeness

The "when" is explicit and detailed, but the description omits the "what" (it never says it writes or creates implementation plans), which is exactly the anchor case of only "when" being present without "what".

2 / 5

Trigger Term Quality

Phrases like "spec", "requirements", "multi-step task", and "before touching code" are reasonably natural keywords, but coverage lacks common synonyms/variations a user might say, fitting the anchor for some relevant keywords with missing variations.

3 / 5

Distinctiveness Conflict Risk

The planning-before-coding niche is mostly distinct, with only minor overlap risk against closely related sibling skills (executing-plans, subagent-driven-development) referenced in the body.

4 / 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
obra/superpowers
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.