| name | re-scoring |
| description | Re-evaluate S/O/D scores after mitigation measures are in place. Validates that mitigations actually reduce risk as expected. |
| execution | subagent |
| prompt | ./prompt.md |
| input | failure_modes (string), mitigations (string), original_scores (string) |
| dependencies | {"sops":["spawn-agent"]} |
Re-Scoring
Re-evaluates Severity, Occurrence, and Detection scores after mitigations are applied.
Execution
Subagent — spawned via subagent-spawning/spawn-agent.
Why Subagent
Re-scoring requires fresh evaluation without anchoring to original scores. Isolated context prevents confirmation bias toward expected improvement.
Input
- failure_modes: Original failure mode descriptions
- mitigations: Proposed mitigation measures
- original_scores: Pre-mitigation S/O/D scores for comparison
Output
- new_scores: Post-mitigation S, O, D, and RPN for each mode
- effectiveness: Comparison with original scores
- still_high: Modes that remain H-priority after mitigation
Available SOPs
Optional, no fixed order; the final leaf is always a sop.
| SOP | When to use |
|---|
| spawn-agent | Spawn a customized CC subagent with full MCP tool access. Used by SOPs that declare execution: subagent. |
