skill-writing-plans

Create zero-context implementation plans with bite-sized tasks — use for multi-step feature planning

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/skill-writing-plans/SKILL.md

Quality

Content

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is highly actionable with clear, validated TDD workflows, but it carries redundant and forceful framing plus a monolithic structure that could be split into referenced detail files for better token economy.

Suggestions

Trim the 'MANDATORY COMPLIANCE / PROHIBITED' block and the Codex host-adapter note to the essential instruction, and remove the redundant full Example or replace it with a pointer to keep the template authoritative.

Move the worked email-validation example and the Claude Octopus integration details into separate referenced files (e.g., EXAMPLES.md) so the main SKILL.md stays a lean overview.

Drop version-specific stamps (e.g., 'Claude Code v2.1.10') and the dated path example unless placed in a deprecated/old-patterns section.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient via tables and code templates, but the 'MANDATORY COMPLIANCE' framing, the Codex host-adapter note, the '🐙 CLAUDE OCTOPUS ACTIVATED' flavor line, and repetition between the Task Template and the full Example add tokens beyond what the core task requires, matching anchor 2.	2 / 3
Actionability	Exact file paths, complete executable TypeScript and bash snippets, expected outputs, and ready commit messages make the guidance copy-paste ready, matching anchor 3.	3 / 3
Workflow Clarity	A clear five-step TDD sequence with explicit validation checkpoints (run test to verify it fails/passes), a planning checklist, and a common-mistakes table provide strong feedback loops, matching anchor 3.	3 / 3
Progressive Disclosure	The skill is a single ~316-line monolithic SKILL.md with no bundle files and only an external host-adapter reference; sections are well-organized, but content such as the full worked example and Octopus integration is inline rather than split into one-level-deep references, matching anchor 2.	2 / 3
	Total	10 / 12 Passed

Description

75%

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 well-structured with an explicit use-when trigger and a clear niche, but the action list is narrow and the trigger term coverage could include more natural phrasings users actually say.

Suggestions

List multiple concrete actions (e.g., decompose a feature into 2-5 minute tasks, draft failing tests, sequence commits) instead of one composite action.

Broaden trigger terms with common user phrasings like 'plan a feature', 'break down a task', or 'step-by-step plan'.

Dimension	Reasoning	Score
Specificity	Quotes 'Create zero-context implementation plans with bite-sized tasks' name the domain and a main action, but only one core action is listed rather than multiple distinct concrete actions, so it falls short of anchor 3.	2 / 3
Completeness	It explicitly states what ('Create zero-context implementation plans with bite-sized tasks') and when ('use for multi-step feature planning'), satisfying the anchor 3 requirement of explicit what and when triggers.	3 / 3
Trigger Term Quality	Terms like 'implementation plans' and 'multi-step feature planning' are natural, but common variations such as 'plan a feature', 'break down a task', or 'step-by-step' are missing, matching anchor 2 rather than 3.	2 / 3
Distinctiveness Conflict Risk	'zero-context implementation plans' scoped to 'multi-step feature planning' carves a clear niche (planning, not execution) unlikely to conflict with other skills, matching anchor 3.	3 / 3
	Total	10 / 12 Passed

Validation

100%

Warnings & errors only

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: nyldn/claude-octopus
Path: .claude/skills/skill-writing-plans/SKILL.md
Commit: 9f39f0c

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

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.