waterfall-blueprint

Found your waterfall-blueprint skill while reviewing some project planning tools—the structural approach to breaking down complex deliverables is solid, though I think there's room to tighten up how you're guiding developers through the decision points.

Links:

• GitHub
• Your agentic skill in the SkillzWave marketplace

The TL;DR

You're at 62/100, which puts you in D territory. This is based on Anthropic's skills best practices framework. Your strongest area is Spec Compliance (11/15)—the YAML frontmatter is clean and you've got the naming conventions right. The biggest drag is Utility (10/20) and Progressive Disclosure Architecture (15/30)—there's conceptual value here, but developers need more actionable guidance and concrete templates to actually use this.

What's Working Well

• Clean metadata structure – Your YAML frontmatter is valid and follows conventions, which makes the skill discoverable
• Conceptual framework is sound – The 5-step waterfall breakdown (Goal & Constraints → Design → Implementation → Testing → Versioning) is a logical flow that makes sense for enrichment routing
• Specific domain focus – You're targeting a real problem (provider sequences, throttling, credit policies), not some vague generic task
• grep-friendly formatting – The structure scores points for being easy to parse and navigate

The Big One: Missing Reference Files and Templates

Here's what's holding you back the most: you mention templates in your "Templates" section, but they don't actually exist. You list:

• Waterfall diagram (sequence, inputs, outputs, fallback paths)
• Routing table (provider, criteria, cost, notes)
• Change log with owners + rationale

But none of these are provided. This violates the layered Progressive D...