writing-plans

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

Quality

53%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./.opencode/skills/writing-plans/SKILL.md

Quality

Discovery

14%

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

This description critically fails to explain what the skill actually does - it only provides vague timing guidance ('before touching code'). The lack of concrete actions and the extremely generic language ('multi-step task') make it nearly impossible for Claude to distinguish this skill from others or understand its purpose.

Suggestions

Add explicit capability statements describing what the skill does (e.g., 'Breaks down specifications into implementation steps, creates task lists, identifies dependencies')

Expand trigger terms to include natural variations users would say: 'spec', 'specification', 'requirements doc', 'PRD', 'planning', 'task breakdown', 'implementation plan'

Restructure to follow the pattern: '[What it does]. Use when [explicit triggers].' to clearly separate capabilities from usage guidance

Dimension	Reasoning	Score
Specificity	The description contains no concrete actions - it only describes when to use the skill ('have a spec or requirements') but never states what the skill actually does. 'Multi-step task' is extremely vague.	1 / 3
Completeness	The description only addresses 'when' (before touching code, when you have specs) but completely fails to explain 'what' the skill does. There is no indication of the skill's actual capabilities or outputs.	1 / 3
Trigger Term Quality	Contains some relevant keywords like 'spec', 'requirements', and 'multi-step task' that users might naturally say, but lacks common variations like 'specification', 'planning', 'breakdown', 'implementation plan', or 'architecture'.	2 / 3
Distinctiveness Conflict Risk	'Multi-step task' and 'before touching code' are extremely generic and could apply to countless skills including planning, architecture, design, task breakdown, or project management skills.	1 / 3
	Total	5 / 12 Passed

Implementation

92%

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, well-structured skill that provides concrete, actionable guidance for writing implementation plans. The task granularity section and template structures are particularly effective. Minor improvement could be made in how external skill references are formatted for clearer navigation.

Suggestions

Convert skill references like 'superpowers:executing-plans' to explicit markdown links (e.g., [executing-plans](../executing-plans/SKILL.md)) for clearer navigation

Dimension	Reasoning	Score
Conciseness	The skill is lean and efficient, using bullet points and code blocks without explaining concepts Claude already knows. Every section serves a clear purpose with no padding or unnecessary context.	3 / 3
Actionability	Provides fully executable templates with exact file paths, complete code examples, specific commands with expected outputs, and copy-paste ready markdown structures for plans.	3 / 3
Workflow Clarity	Clear multi-step workflow with explicit sequence: write plan → save to specific path → create epic → offer execution handoff. Each task structure includes numbered steps with validation (run test, verify fail/pass) and commit checkpoints.	3 / 3
Progressive Disclosure	References other skills appropriately (executing-plans, subagent-driven-development, epic-creation) but doesn't use clear link formatting. The content is well-organized but could better signal where to find referenced skills.	2 / 3
	Total	11 / 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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: projectbluefin/dakota
Commit: f062bf8

Reviewed: 11 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.