Design document review format definition with 100-point scoring system. Provides quality evaluation criteria, scoring items, and pass/fail logic for SOW/Spec documents. Combined with confidence markers (✓/→/?) to clarify evaluation evidence. Triggers: SOW review, Spec review, document review, design review, ドキュメントレビュー, 設計レビュー, 90 points, scoring, grading, 品質評価, スコアリング, 合否判定.
/plugin marketplace add thkt/claude-config/plugin install complete-workflow-system@thkt-development-workflowsThis skill is limited to using the following tools:
EVALUATIONS.md100-point scoring format for evaluating SOW/Spec document quality.
| Item | Score | Focus | Criteria |
|---|---|---|---|
| Accuracy | 0-25 | Facts vs inferences | ✓/→/? markers, evidence paths |
| Completeness | 0-25 | Coverage | Testable criteria, risks, dependencies |
| Relevance | 0-25 | Alignment | Goals ↔ solutions, scope, YAGNI |
| Actionability | 0-25 | Implementability | Specific steps, feasibility, next actions |
| Score | Judgment | Action |
|---|---|---|
| 90-100 | PASS | Proceed to next phase |
| 70-89 | CONDITIONAL | Re-review after fixes |
| 0-69 | FAIL | Major revision needed |
| Score Range | Quality Level |
|---|---|
| 23-25 | Excellent - All claims have evidence |
| 18-22 | Acceptable - Most claims verified |
| 13-17 | Needs work - Multiple gaps |
| 0-12 | Insufficient - Major issues |
## 📋 Design Document Review Result
### Total Score: {total}/100 {✅/⚠️/❌}
| Item | Score | Marker |
| ------------- | ----- | ------ |
| Accuracy | /25 | ✓/→/? |
| Completeness | /25 | ✓/→/? |
| Relevance | /25 | ✓/→/? |
| Actionability | /25 | ✓/→/? |
### 🔗 SOW ↔ Spec Consistency
| Check | Status |
| ------------------------ | ------ |
| Acceptance Criteria → FR | ✓/→/? |
| Risks → Mitigations | ✓/→/? |
| Dependencies | ✓/→/? |
| Test Coverage | ✓/→/? |
### 📝 Requested Modifications
🔴 Required: [list]
🟡 Recommended: [list]
### Next Action
✅ PASS: /code
⚠️ CONDITIONAL: Fix and re-review
❌ FAIL: Re-plan with /think
reviewing-readability - Readability review skillsow-spec-reviewer - SOW/Spec verification agent/think - SOW/Spec generation/audit - Code review orchestrationThis skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.