CtrlK
BlogDocsLog inGet started
Tessl Logo

writing-plans

Creates detailed, bite-sized implementation plans with TDD structure, exact file paths, complete code, and test commands. Use when you have a spec, requirements, design doc, or feature request and need to plan before coding — especially for multi-step tasks, large features, or when handing off to another session. DO NOT TRIGGER when asked to write code directly or fix a simple bug.

80

Quality

100%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

100%

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 tight, actionable planning template with explicit TDD sequencing, validation checkpoints, and concrete commands throughout. Organization is clear and self-contained with no unnecessary fluff.

DimensionReasoningScore

Conciseness

The body is lean: bullets and compact templates carry the instruction, it assumes developer competence ("DRY. YAGNI. TDD."), and it never pads with concepts Claude already knows.

3 / 3

Actionability

It provides copy-paste-ready templates with exact paths (`exact/path/to/file.py`), concrete commands (`pytest tests/path/test.py::test_name -v`), and expected outputs, satisfying the fully-executable level-3 anchor.

3 / 3

Workflow Clarity

The TDD sequence (write failing test → verify fail → implement → verify pass) is explicitly ordered with validation checkpoints ("Expected: FAIL" / "Expected: PASS") and reinforced by "Common Mistakes" and "Remember" checklists.

3 / 3

Progressive Disclosure

A single self-contained file with no external bundle references and clearly labeled sections (Overview, Granularity, Header, Task Structure, Remember, Common Mistakes, Execution Handoff) is well-organized with nothing nested.

3 / 3

Total

12

/

12

Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A high-quality description that is specific, uses third-person voice, supplies explicit positive and negative triggers, and cleanly answers both what the skill does and when to use it. No notable weaknesses.

DimensionReasoningScore

Specificity

"Creates detailed, bite-sized implementation plans with TDD structure, exact file paths, complete code, and test commands" lists multiple concrete capabilities rather than vague actions, matching the level-3 anchor.

3 / 3

Completeness

It explicitly answers both what (creates plans with TDD structure, paths, code, test commands) and when ("Use when you have a spec, requirements, design doc, or feature request"), satisfying the level-3 anchor.

3 / 3

Trigger Term Quality

Natural trigger phrases like "spec, requirements, design doc, or feature request", "plan before coding", "multi-step tasks, large features", plus a negative trigger cover the terms a user would actually say.

3 / 3

Distinctiveness Conflict Risk

The pre-coding planning niche is distinct and the explicit "DO NOT TRIGGER when asked to write code directly or fix a simple bug" clause sharply reduces conflict with adjacent skills.

3 / 3

Total

12

/

12

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
shousper/claude-kit
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.