confidence-scoring

# Confidence Scoring for PRPs and Work-Orders

This skill provides systematic evaluation of PRPs (Product Requirement Prompts) and work-orders to determine their readiness for execution or delegation.

## When to Use This Skill

Activate this skill when:
- Creating a new PRP (`/prp:create`)
- Generating a work-order (`/blueprint:work-order`)
- Deciding whether to execute or refine a PRP
- Evaluating whether a task is ready for subagent delegation
- Reviewing PRPs/work-orders for quality

## Scoring Dimensions

### 1. Context Completeness (1-10)

Evaluates whether all necessary context is explicitly provided.

| Score | Criteria |
|-------|----------|
| **10** | All file paths explicit with line numbers, all code snippets included, library versions specified, integration points documented |
| **8-9** | Most context provided, minor gaps that can be inferred from codebase |
| **6-7** | Key context present but some discovery required |
| **4-5** | Significant context missing, will need exploration |
| **1-3** | Minimal context, extensive discovery needed |

**Checklist**:
- [ ] File paths are absolute or clearly relative to project root
- [ ] Code snippets include actual line numbers (e.g., `src/auth.py:45-60`)
- [ ] Library versions are specified
- [ ] Integration points are documented
- [ ] Patterns from codebase are shown with examples

### 2. Implementation Clarity (1-10)

Evaluates how clear the implementation approach is.

| Score | Criteria |
|-------|----------|
| **10** | Pseudocode covers all cases, step-by-step clear, edge cases addressed |
| **8-9** | Main path clear, most edge cases covered |
| **6-7** | Implementation approach clear, some details need discovery |
| **4-5** | High-level only, significant ambiguity |
| **1-3** | Vague requirements, unclear approach |

**Checklist**:
- [ ] Task breakdown is explicit
- [ ] Pseudocode is provided for complex logic
- [ ] Implementation order is specified
- [ ] Edge cases are identified
- [ ] Error handling appro