confidence-scoringlisted

# 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 | Use this skill when... | Use `blueprint-prp-create` instead when... | |---|---| | Scoring a draft PRP/work-order before execution or delegation | Authoring the PRP itself from research and context | | Deciding whether a work-order is ready for a subagent or needs refinement | Producing the work-order content (use `blueprint-work-order`) | | Reviewing existing PRPs/work-orders for context completeness and validation gates | Generating the PRD that the PRP derives from (use `blueprint-derive-plans`) | ## 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 sp