Before you hand Claude a spec to build from, run it through this scoring server. It rates your spec on four axes (completeness, clarity, constraints, specificity) and returns a balance score with a radar chart visualization. The verdict tells you if you're ready to ship or which axis needs work. Three tools: spec_score for analysis, spec_visualize for SVG charts, spec_compare for side-by-side diffs. The insight here is that balance matters more than high scores on individual axes. A spec that's 0.95 on goals but 0.20 on constraints will make Claude improvise features you never asked for. Catch lopsided specs before they become lopsided code.
claude mcp add --transport stdio openpoem-spec-score-mcp uvx spec-score-mcp