一键在 Manus 中运行任何 Skill

doncheli-spec-score

星标56

分支10

更新时间2026年4月1日 17:09

Evaluate the quality of a spec and return a structured score with improvement recommendations. Activate when user mentions "spec quality", "score spec", "how good is my spec", "spec review", "validate spec quality".

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

在 Manus 中运行

来源

doncheli

doncheli/don-cheli-sdd

打开 GitHub 仓库查看创作者相关仓库

下载

在 Manus 中运行

Don Cheli: Spec Score

Instructions

Accept a spec file path or read the current spec from .dc/specs/
Evaluate the spec across 5 dimensions (0–10 each):
- Completeness: all scenarios covered, no missing edge cases
- Clarity: unambiguous language, no "should", "may", "probably"
- Testability: each scenario has a verifiable, binary outcome
- Consistency: no contradictions between scenarios or with existing specs
- Scope control: no out-of-scope behavior mixed in, single responsibility
For each dimension below 7, provide 2–3 specific improvement suggestions with line references
Compute a weighted total score (Completeness 30%, Clarity 25%, Testability 25%, Consistency 10%, Scope 10%)
Assign a grade: A (90-100), B (75-89), C (60-74), D (below 60)
Grade D specs must be improved before implementation — flag as a hard blocker
Optionally save the score card to .dc/spec-scores/<spec-name>-<date>.md

Output Format

## Spec Score — checkout.feature — 2026-03-28

### Scores
| Dimension     | Score | Weight | Weighted |
|--------------|-------|--------|---------|
| Completeness  |   8   |  30%   |   2.4   |
| Clarity       |   6   |  25%   |   1.5   |
| Testability   |   9   |  25%   |   2.25  |
| Consistency   |   7   |  10%   |   0.7   |
| Scope Control |   8   |  10%   |   0.8   |
| **Total**     |       |        | **7.65**|

### Grade: B

### Improvement Suggestions

**Clarity (score: 6)**
- Line 14: "the system should respond quickly" — define SLA (e.g., "within 200ms")
- Line 28: "valid payment method" — list accepted types explicitly

### Verdict
Spec is implementation-ready with minor clarity fixes recommended.

同仓库更多 Skills

同仓库

doncheli-prd

doncheli/don-cheli-sdd

Generate professional Product Requirement Documents (PRD) from multiple sources — Figma designs, briefs, user research, existing code. Includes risk analysis, RICE prioritization, Gherkin stories and launch plan. Activate when user mentions "PRD", "product requirements", "requirement document", "product spec", "figma to PRD", "generate PRD".

2026-04-0756

doncheli-audit-trail

doncheli/don-cheli-sdd

Record and query the decision log for a project. Activate when user mentions "audit", "trail", "log decisions", "decision history", "why was this decided", "ADR", "architecture decision".

2026-04-0156

doncheli-data-policy

doncheli/don-cheli-sdd

Audit and document what personal or sensitive data the project collects, processes, and stores. Activate when user mentions "privacy", "data policy", "what data", "GDPR", "personal data", "data retention", "PII".

2026-04-0156

doncheli-drift

doncheli/don-cheli-sdd

Detect and reconcile divergence between specs and implementation. Activate when user mentions "drift", "sync", "spec divergence", "out of sync", "spec doesn't match", "implementation differs".

2026-04-0156

doncheli-estimate

doncheli/don-cheli-sdd

Estimate effort, duration and cost using 4 complementary models (Function Points, Planning Poker AI, COCOMO, Historical). Activate when user mentions "estimate", "estimation", "effort", "how long", "cost", "story points", "sizing".

2026-04-0156

doncheli-tea

doncheli/don-cheli-sdd

Run the full autonomous test suite end-to-end and report results. Activate when user mentions "test end to end", "autonomous testing", "run all tests", "full test run", "E2E tests", "test suite".

2026-04-0156

name	doncheli-spec-score
description	Evaluate the quality of a spec and return a structured score with improvement recommendations. Activate when user mentions "spec quality", "score spec", "how good is my spec", "spec review", "validate spec quality".

Don Cheli: Spec Score

Instructions

Accept a spec file path or read the current spec from .dc/specs/
Evaluate the spec across 5 dimensions (0–10 each):
- Completeness: all scenarios covered, no missing edge cases
- Clarity: unambiguous language, no "should", "may", "probably"
- Testability: each scenario has a verifiable, binary outcome
- Consistency: no contradictions between scenarios or with existing specs
- Scope control: no out-of-scope behavior mixed in, single responsibility
For each dimension below 7, provide 2–3 specific improvement suggestions with line references
Compute a weighted total score (Completeness 30%, Clarity 25%, Testability 25%, Consistency 10%, Scope 10%)
Assign a grade: A (90-100), B (75-89), C (60-74), D (below 60)
Grade D specs must be improved before implementation — flag as a hard blocker
Optionally save the score card to .dc/spec-scores/<spec-name>-<date>.md

Output Format

## Spec Score — checkout.feature — 2026-03-28

### Scores
| Dimension     | Score | Weight | Weighted |
|--------------|-------|--------|---------|
| Completeness  |   8   |  30%   |   2.4   |
| Clarity       |   6   |  25%   |   1.5   |
| Testability   |   9   |  25%   |   2.25  |
| Consistency   |   7   |  10%   |   0.7   |
| Scope Control |   8   |  10%   |   0.8   |
| **Total**     |       |        | **7.65**|

### Grade: B

### Improvement Suggestions

**Clarity (score: 6)**
- Line 14: "the system should respond quickly" — define SLA (e.g., "within 200ms")
- Line 28: "valid payment method" — list accepted types explicitly

### Verdict
Spec is implementation-ready with minor clarity fixes recommended.