feature-dev

I took a look at your feature-dev skill and wanted to share some thoughts.

Links:

• GitHub
• SkillzWave marketplace

TL;DR

You're at 62/100, which puts you in D territory. This skill has solid bones—your Utility pillar scored 18/20, which is really strong, and your workflow thinking is clear. But you're getting hammered on Spec Compliance (0/15) and Progressive Disclosure Architecture (12/30). The good news? These are fixable issues, not conceptual ones.

What's Working Well

• Utility is legit (18/20) — Your 7-phase workflow actually addresses real gaps in feature development, and the agent specialization (code-explorer, code-architect, code-reviewer) is practical
• Good trigger phrases — Your activation keywords are specific and discoverable; someone will actually find this when they need it
• Solid examples — You've included concrete output examples that show how the agents work together, which is helpful for understanding the workflow
• Clear instructions — The step-by-step breakdown is easy to follow; this isn't a vague skill

The Big One: Frontmatter is Broken

Your SKILL.md has invalid YAML frontmatter. The grader literally can't parse it, which automatically tanks you 15 points on Spec Compliance. Here's the fix:

Current (broken):

---
name: feature-dev
description: Automate 7-phase feature development with specialized agents (code-explorer, code-architect, code-reviewer). Use for multi-file features, architectural decisions, or

Should be:

---
name: feature-dev
description: Automate feature development across 7 phases using specialized agents. Use when asked to "build a feature", "architect a complex feature", "design multi-file features", or "review feature implementations".
keywords: ["feature development", "architecture", "code review", "multi-agent workflow"]
required-context: true
---

Close that YAML block properly, complete the description with clear trigger phrases, and add keywords. This alone gets you +5 points.

Other Things Worth Fixing

1. Missing referenced files — You mention README.md, agents/*.md, and commands/*.md throughout, but these don't exist in the repo. Either create them (which adds nice layered structure) or remove the references. This is costing you points on Progressive Disclosure Architecture.

2. No table of contents — Your SKILL.md is 325 lines without a TOC. For something this long, readers need navigation signals. Add a quick markdown TOC at the top so people can jump to phases, workflow steps, or examples.

3. Incomplete reference depth — The PDA pillar expects supporting documentation files. Create a simple README.md that explains the overall approach, or break the SKILL.md into sections with clear "learn more here" pointers. Right now it reads like a wall of text.

4. Workflow checklist needs completion — You've numbered 7 phases but the verification section feels rushed. Flesh out what "success" looks like for each phase with concrete acceptance criteria.

Quick Wins

• Fix the YAML frontmatter (+5 points immediately)
• Add a TOC and reference files (+5 points)
• Flesh out the description with trigger phrases (+4 points)
• Complete the verification checklist (+3 points)

These four moves should push you into B territory pretty easily. Your core idea is solid—it's just the packaging that needs work.

Checkout your skill here: SkillzWave.ai | SpillWave We have an agentic skill installer that install skills in 14+ coding agent platforms. Check out this guide on how to improve your agentic skills.