10 actions in 9 pieces of software · ranked by words, meaning and measured trust · 704 ms
- 14-specdemo or tutorialno passport yet
skillchallengepost/learn-ai-basicsrecord
- 4-spec
Turn the approved PRD into a technical blueprint the build can follow — stack, where it runs, components, data, file structure — calibrated to the learner and sized to a proof of concept. The last planning step before code. Run after 3-prd.
- 4-spec
- 2Spec Score MCPfound in code, not yet checkedno passport yet
MCP serveropenpoem/spec-score-mcp
- spec_score
Score a spec/requirement on 4 axes. YOU (the LLM) read the spec and score it. Score the spec on these 4 axes (each 0.0-1.0): - completeness: Can an LLM understand the full scope? (0=vague idea, 1=complete with goal+context+criteria) - clarity: Is it unambiguous? (0=multiple interpretations, 1=one cl
- spec_compare
Side-by-side radar charts comparing two specs. YOU (the LLM) score BOTH specs on 4 axes each. Useful for before/after or good/bad examples.
- spec_score
- implement-spec
Implement the result of /to-spec and /to-tickets in code.
- implement-spec
skillanthropics/knowledge-work-pluginsrecord
- write-spec
Write a feature spec or PRD from a problem statement or feature idea. Use when turning a vague idea or user request into a structured document, scoping a feature with goals and non-goals, defining success metrics and acceptance criteria, or breaking a big ask into a phased spec.
- write-spec
skillvinvcn/mattpocock-skills-zh-cnrecord
- implement-spec
在代码中实现 /to-spec 和 /to-tickets 的产出。
- implement-spec
skillcodewithmukesh/dotnet-claude-kitrecord
- spec
Turn a vague feature or product idea into an agreed, persisted specification through relentless structured questioning. Never assumes — every gap, ambiguity, or "probably" becomes a question to the developer, and the spec cannot be approved while open questions remain. Produces docs/specs/<NNN>-<slu
- spec
skillanthropics/knowledge-work-pluginsrecord
- feature-spec
Write structured product requirements documents (PRDs) with problem statements, user stories, requirements, and success metrics. Use when speccing a new feature, writing a PRD, defining acceptance criteria, prioritizing requirements, or documenting product decisions.
- feature-spec
skillvinvcn/mattpocock-skills-zh-cnrecord
- to-spec
把当前对话转成 spec 并发布到项目 issue tracker:不做访谈,只综合已经讨论的内容。
- to-spec
- to-spec
Turn the current conversation into a spec published to the project tracker — no interview, just synthesis of what was already discussed.
- to-spec
Labels are the instruments' verdict and are never changed by ranking. Agents and robots get this same answer as JSON at /api/v1/find?q=…&answer=1 and through the MCP server.