doc-requirements-matrix

I took a look at your requirements documentation skill—the structured approach to capturing product needs is solid, but the modularity could use some work. With a 54/100, there's a real opportunity here to tighten how the different components fit together and make the whole thing more intuitive for teams actually trying to use it.

Links:

• GitHub
• Your agentic skill in the SkillzWave marketplace

The TL;DR

You're at 54/100, firmly in F territory. This is based on Anthropic's progressive disclosure and spec compliance best practices. Your strongest area is Spec Compliance (11/15)—the frontmatter is solid and naming conventions are clean. The real weak spots are Utility (8/20) and Progressive Disclosure Architecture (13/30)—you're describing what the skill does, but not giving users the actual tools to do it.

What's Working Well

• Clean frontmatter structure – Valid YAML with required fields; the naming convention (doc-requirements-matrix) follows hyphen-case correctly
• Clear conceptual framework – The five-step process (Request Intake → Scoring → Priority Board → Assignment → Tracking) is logical and addresses a real pain point
• Consistent terminology – Terms like 'request', 'scoring', and 'status' stay consistent throughout, which helps users understand the flow

The Big One: Missing Reference Files and Scoring Details

Here's what's killing your utility score: you're talking about templates and scoring formulas, but they don't actually exist anywhere. The "Templates" section says:

Requirement intake form (Notion/Sheet) with scoring formula.
Priority board with filters...

But there's no references/ directory with the actual intake form template, no scoring formula breakdown, no worked examples. This viol...