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 findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/agent-code-goal-planner/SKILL.md

Quality

Content

27%Scale 1-3

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, attempting to be a comprehensive reference document rather than a focused, actionable skill. It explains numerous concepts Claude already understands (GOAP, sprint planning, git workflows, test pyramids) and includes extensive template-like examples that are illustrative rather than executable. The content would benefit enormously from aggressive trimming to its core purpose and splitting detailed reference material into separate files.

Suggestions

Reduce the skill to under 100 lines by removing explanations of concepts Claude already knows (GOAP methodology, sprint planning, git branching, test pyramids, delivery metrics) and keeping only the SPARC-specific workflow and CLI commands.

Split detailed reference material (Success Metrics Framework, SPARC Mode descriptions, Planning Patterns) into separate bundle files and reference them with clear links from the main SKILL.md.

Add explicit validation/feedback loops to the workflow: what to check after each SPARC phase, how to detect failure, and what corrective action to take before proceeding.

Make code examples truly executable rather than illustrative — the MCP tool invocations use non-standard syntax and the TypeScript/JavaScript classes are abstract patterns rather than runnable code.

Dimension	Reasoning	Score
Conciseness	Extremely verbose at ~350+ lines. Explains basic concepts like GOAP methodology, SPARC phases, git branching strategies, and sprint planning that Claude already knows. Massive amounts of illustrative YAML/code that are template-like rather than actionable. The description frontmatter alone contains lengthy examples that belong in the body if anywhere.	1 / 3
Actionability	Contains concrete code examples and CLI commands (e.g., `npx claude-flow sparc run`), but most are illustrative templates rather than executable guidance. The TypeScript interfaces and JavaScript classes are pseudocode-level abstractions showing planning patterns rather than copy-paste-ready implementations. MCP tool invocations use non-standard syntax that isn't clearly executable.	2 / 3
Workflow Clarity	The SPARC phases provide a clear sequence (Specification → Pseudocode → Architecture → Refinement → Completion), and the bash example at the end shows a numbered workflow. However, there are no explicit validation checkpoints or feedback loops for error recovery. The skill describes planning but doesn't include verification steps like 'if milestone fails, do X' beyond mentioning TDD abstractly.	2 / 3
Progressive Disclosure	Monolithic wall of content with no references to external files and no bundle files provided. Everything is inlined — YAML plans, code examples, metrics frameworks, risk assessment, workflow integration — creating an overwhelming document that should be split into focused reference files. Multiple sections (Success Metrics, Risk Assessment, SPARC Modes) could easily be separate documents.	1 / 3
	Total	6 / 12 Passed

Description

0%Scale 1-3

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 placeholder that provides no useful information about the skill's capabilities, use cases, or trigger conditions. It only states the invocation command and an internal name, making it impossible for Claude to determine when to select this skill over others. This is among the weakest possible descriptions.

Suggestions

Add concrete actions describing what the skill does, e.g., 'Breaks down coding goals into step-by-step implementation plans, identifies required files and dependencies, and generates task lists for complex code changes.'

Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user wants to plan a coding task, break down a feature into steps, create an implementation roadmap, or organize a complex code change.'

Replace the internal tool name reference with a human-readable description of the skill's domain and purpose to improve distinctiveness and trigger matching.

Dimension	Reasoning	Score
Specificity	The description provides no concrete actions whatsoever. 'Agent skill for code-goal-planner' is entirely vague 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 invocation command and the skill's internal name, providing no functional or contextual information.	1 / 3
Trigger Term Quality	There are no natural keywords a user would say. 'code-goal-planner' is a technical internal name, not a term users would naturally use in requests. The description lacks any domain-specific trigger terms.	1 / 3
Distinctiveness Conflict Risk	The description is so vague that it could overlap with any code-related or planning-related skill. There are no distinct triggers or niche identifiers to differentiate it.	1 / 3
	Total	4 / 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
Path: .agents/skills/agent-code-goal-planner/SKILL.md
Commit: 913f9ea

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