Confidence Assessment

Rate your confidence that the current work fully solves the stated requirement. Plan mode is gated on two signals — LLM dimensional scoring and deterministic rule checks; rationale: references/multi-signal-rationale.md.

Contents: Mode Detection · Assessment Dimensions · Output Format · Score Thresholds · Iteration Protocol

Mode Detection

Check the arguments: $ARGUMENTS

If no argument is provided, default to code.

Alias handling. bug-analysis resolves to analysis with identical dimensions, weights, thresholds, and Fix Mode behaviour. When invoked with the alias, prepend a single line to the report header: > Note: \bug-analysis` is a deprecated alias for `analysis`. Update the caller when convenient.`

If arguments contain "fix" (e.g., code fix, plan fix, analysis fix), run in Fix Mode: after the review, apply fixes for every concern found — read rules/fix-mode.md when in Fix Mode.

Assessment Dimensions

For plan mode

Both signals must pass for the gate to clear.

Step 1 — LLM dimensional scoring

Step 2 — Deterministic rule checks (run via Bash). Run all 11 rules in rules/plan-rule-checks.md — read it in every plan-mode run. A single failed rule caps the gate at 89% regardless of LLM score; surface the failed rule and either fix the plan or escalate to the user.

Step 3 — Combined gate

overall_score = min(weighted_LLM_score, max_allowed_by_rule_checks)
where max_allowed_by_rule_checks = 100% if all rules pass, else 89%

For code mode

For analysis mode

Use when the graded artifact is an analysis — a root-cause write-up, a refactor rationale, a /create-skill diagnose proposal, a holistic re-analysis after a stuck loop, or any reasoning artifact that precedes a proposed change.

Output Format

Output in this exact format:

## Confidence: X%

### LLM dimensional scoring

| Dimension | Score | Notes |
|-----------|-------|-------|
| <dim 1>   | X%    | ...   |
| <dim 2>   | X%    | ...   |
| <dim 3>   | X%    | ...   |

### Deterministic rule checks (plan mode only — omit for code/analysis)

| # | Rule                | Status      | Evidence                  |
|---|---------------------|-------------|---------------------------|
| 1 | <rule description>  | ✓ pass / ✗ fail | <command output snippet> |
| ... |                   |             |                           |

### Combined gate

- Weighted LLM score: X%
- Rule checks: <N pass> / <total> (cap: 100% if all pass, else 89%)
- **Final: X%**

The weighted LLM score is the weighted average over the dimension weights above. For plan mode, Final is min(weighted_LLM_score, rule_check_cap). For code and analysis modes (including the deprecated bug-analysis alias), omit the rule-check section and Final = weighted_LLM_score.

Do not inflate scores: a low score with clear reasoning beats a false 95%, and a failed rule check is always surfaced, even when the LLM score is high.

Score Thresholds

Iteration Protocol (plan mode)

When used as a quality gate before autonomous execution:

If confidence is below 90%, do up to 2 iterations of additional research, analysis, and evidence collection to raise the score. After each iteration, re-run the confidence assessment. If still below 90% after 2 iterations, present findings to the user and ask whether to proceed or refine further.