CtrlK
BlogDocsLog inGet started
Tessl Logo

writing-plans

当你有规格说明或需求用于多步骤任务时使用,在动手写代码之前

55

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

92%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.

This is a strong, highly actionable planning skill: concrete templates, a clear end-to-end workflow, and explicit validation/feedback loops. Its only weakness is mild verbosity in a few philosophical passages that explain concepts Claude already knows.

DimensionReasoningScore

Conciseness

The body is mostly efficient with concrete templates and terse principle reminders, but contains minor over-explanation of concepts Claude knows (e.g. "你对能一次放入上下文的代码推理得最好,文件越专注你的编辑越可靠" justifies why small files help), matching the 'efficient with minor trimmable instances' anchor.

4 / 5

Actionability

It provides copy-paste-ready templates with concrete commands — real pytest invocations ("pytest tests/path/test.py::test_name -v"), git add/commit commands, exact file-path placeholders, and a full plan-header template — fully executable guidance covering the common cases.

5 / 5

Workflow Clarity

The process is clearly sequenced (范围检查 → 文件结构 → 任务分解 → 自检 → 执行交接) with an explicit self-check checklist (规格覆盖度, 占位符扫描, 类型一致性), per-step FAIL→PASS validation, and a feedback loop ("如果发现问题,直接内联修复"; add tasks for uncovered requirements).

5 / 5

Progressive Disclosure

No bundle files exist and none are needed — the skill is a self-contained methodology with well-organized section headers and only one-level references to sibling skills (subagent-driven-development, executing-plans, brainstorming), so well-organized sections fully satisfy progressive disclosure.

5 / 5

Total

19

/

20

Passed

Description

36%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 clause with natural timing guidance, but it omits what the skill actually does — it never mentions creating implementation plans, leaving the reader to infer its purpose entirely.

Suggestions

Add a 'what' clause stating the skill's output, e.g. prepend '编写全面的实现计划' so the description reads as '编写全面的实现计划。当你有规格说明或需求用于多步骤任务时使用,在动手写代码之前。'

Include synonyms users naturally say — '计划', '实现计划', '设计文档' — to improve trigger coverage beyond '规格说明/需求/多步骤任务'.

Reframe in third person and combine what + when in one sentence (e.g. '为多步骤任务编写分步骤的实现计划。当有规格说明或需求、在动手写代码之前使用。') to lift completeness to a 4-5.

DimensionReasoningScore

Specificity

The description names the domain ("规格说明或需求用于多步骤任务", "动手写代码之前") but states zero concrete actions — it never says the skill writes or produces anything, so it sits below the anchor that expects at least minimal/generic actions.

2 / 5

Completeness

It provides an explicit "when" ("当你有规格说明或需求...时使用") but no "what" — the skill's purpose of producing an implementation plan is never stated, matching the anchor for "only 'when' is present without 'what'".

2 / 5

Trigger Term Quality

It includes relevant natural keywords ("规格说明", "需求", "多步骤任务", "写代码之前") a user might say, but lacks common synonyms like "计划", "实现计划", or "设计文档", matching the anchor for some-but-incomplete keyword coverage.

3 / 5

Distinctiveness Conflict Risk

The "have a spec, before writing code" trigger is somewhat specific to a planning skill, but "多步骤任务" is broad and could overlap with sibling skills like executing-plans or brainstorming, matching the "somewhat specific but could still overlap" anchor.

3 / 5

Total

10

/

20

Passed

Validation

81%

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

Validation13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

13

/

16

Passed

Repository
jnMetaCode/superpowers-zh
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.