agent-code-goal-planner

Agent skill for code-goal-planner - invoke with $agent-code-goal-planner

2.28x

Quality

13%

Does it follow best practices?

Impact

89%

2.28x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./.agents/skills/agent-code-goal-planner/SKILL.md

Quality

Discovery

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 is essentially a label and invocation command with no substantive content. It fails on every dimension: it does not describe what the skill does, when to use it, or provide any natural trigger terms. It would be nearly impossible for Claude to correctly select this skill from a pool of available skills.

Suggestions

Add a clear 'what' clause describing the concrete actions this skill performs (e.g., 'Breaks down coding goals into step-by-step implementation plans, identifies dependencies, and generates task lists').

Add an explicit 'Use when...' clause with natural trigger terms (e.g., 'Use when the user wants to plan a coding project, break down a feature into tasks, or create an implementation roadmap').

Remove the invocation syntax from the description and replace it with user-facing language that describes the skill's purpose and distinguishes it from other code-related skills.

Dimension	Reasoning	Score
Specificity	The description contains no concrete actions whatsoever. 'Agent skill for code-goal-planner' is entirely abstract and does not describe what the skill actually does.	1 / 3
Completeness	Neither 'what does this do' nor 'when should Claude use it' is answered. The description only states the skill's name and invocation command, providing no functional or contextual information.	1 / 3
Trigger Term Quality	There are no natural keywords a user would say. 'code-goal-planner' is an internal tool name, not a term users would naturally use in requests. The invocation syntax '$agent-code-goal-planner' is technical jargon.	1 / 3
Distinctiveness Conflict Risk	The description is so vague that it could overlap with any code-related skill. 'Code-goal-planner' gives a hint of domain but is not specific enough to distinguish it from other planning, coding, or goal-setting skills.	1 / 3
	Total	4 / 12 Passed

Implementation

27%

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

This skill is excessively verbose and highly repetitive, restating the SPARC-GOAP integration concept across at least 4-5 overlapping sections. While it contains some useful structural templates (YAML plans, TypeScript interfaces, CLI commands), the signal-to-noise ratio is very low. The content would benefit enormously from aggressive deduplication, splitting into referenced sub-files, and removing explanations of concepts Claude already understands.

Suggestions

Reduce content by 60-70% by eliminating redundant sections - consolidate 'SPARC Phases in Goal Planning', 'SPARC-Enhanced Planning Patterns', 'SPARC Mode-Specific Goal Planning', and 'SPARC-GOAP Synergy' into a single concise section with one clear example.

Split detailed reference material (Success Metrics Framework, Planning Patterns, MCP Tool Integration) into separate referenced files, keeping SKILL.md as a concise overview with links.

Add explicit validation checkpoints and error recovery steps to workflows - e.g., 'If specification review reveals ambiguity, iterate before proceeding to architecture phase.'

Remove explanations of well-known concepts (test pyramids, cyclomatic complexity, DORA metrics, sprint planning) and focus only on the specific SPARC-GOAP methodology and tool commands that are unique to this skill.

Dimension	Reasoning	Score
Conciseness	Extremely verbose at ~350+ lines. Massive amounts of redundant content - the SPARC methodology is explained multiple times, the same concepts are restated across sections (e.g., 'SPARC Phases in Goal Planning', 'SPARC-Enhanced Planning Patterns', 'SPARC Mode-Specific Goal Planning', 'SPARC-GOAP Synergy' all overlap heavily). Explains concepts Claude already knows like what test pyramids are, what cyclomatic complexity means, and basic sprint planning. Much of this could be condensed to 1/4 the size.	1 / 3
Actionability	Contains concrete code examples and CLI commands (e.g., `npx claude-flow sparc run spec-pseudocode`), YAML planning templates, and TypeScript interfaces. However, much of the code is illustrative pseudocode rather than truly executable (e.g., the SPARCGoalPlanner class references undefined methods, the MCP tool calls use non-standard syntax). The YAML plans are templates/examples rather than directly usable artifacts.	2 / 3
Workflow Clarity	There are multiple workflow sequences presented (SPARC phases 1-5, the bash example at the end, the YAML milestone plans), but they lack explicit validation checkpoints and error recovery steps. The workflows show a linear happy path without feedback loops for when things go wrong. For a planning skill involving complex multi-step development processes, the absence of 'if X fails, do Y' patterns is a notable gap.	2 / 3
Progressive Disclosure	This is a monolithic wall of text with no references to external files. All content is inline despite being extremely long. There's no separation between quick-start/overview content and detailed reference material. The numerous sections (Core Competencies, Planning Patterns, Workflow Integration, Success Metrics, Mode-Specific Planning, SPARC-GOAP Synergy) could easily be split into referenced sub-documents.	1 / 3
	Total	6 / 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: ruvnet/claude-flow
Commit: 322b2ae

Reviewed: 1 day 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.