fix(planning): word the round's closing probe as 'something else'

Chiusa Adatta ai principianti
  • Qualcosa non va?
#11,191 2 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
2/5
Tempo stimato
1-3 ore
Idoneità per principianti
74/100
Tipo di issue
Bug
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
markdown, shell
Ambito
ai-infra-agents, tooling

Direzione di ricerca

Leggi plugins/planning/skills/interview/context/loop.md, in particolare “Constraint probe kept” e la definizione di closing-probe. Indica una volta la formulazione richiesta “something else” e cita interview-closing-probe-something-else come evidenza di valutazione. Esegui scripts/check-affected.sh --tests e scripts/check-changelog-fragments.sh; il lavoro è completato quando entrambi passano, incluso l’eventuale aggiornamento di un digest fissato.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

host-run priority: medium status: ready work-class: scoped

Parent: #9794 (split from #7269, now closed). Eval-first case interview-closing-probe-something-else from #7247 fails on main; #7303's eval-first page items depend on these results.

Problem

The round's closing probe is not worded "something else". With the plugin, runs avoided "anything else" but closed with other wording (such as "Is there a constraint I've missed...?") or no probe at all. The case's rationale cites Heritage et al. 2007: "Is there something else...?" left fewer concerns unmet than "Anything else?".

Change

In plugins/planning/skills/interview/context/loop.md, at "Constraint probe kept" and wherever the closing probe is defined, give its wording: "Is there something else that would change these recommendations?" (or a close variant using "something else"), never "anything else".

Evidence

Host run on 2026-10-30, Claude Code 2.1.314, claude plugin eval against an out-of-git copy of plugins/planning at 543166dde6, --runs 3 --judge-model opus --threshold 0.8, default with/without ablation. run-validity.py: VALID (warning: skill fired, since the slash command loads the hub without a Skill tool call; the with-arm output follows the hub's procedure). Scores: with 0.50, without 0.50, delta 0; says-something-else 0 of 3 and no-anything-else 3 of 3 in both arms. No with-arm tool call errored or was denied, including every read under skills/interview/context/, so the result is not the bare-path defect. Judge uncalibrated. Full record on #9794.

Done when

  • The rule above is in the named spoke (or hub line), stated once, with the case named as its eval evidence.
  • scripts/check-affected.sh --tests passes on the committed head, including plugins/planning/tests/interview-defenses.test.sh with any digest it pins re-pinned.
  • scripts/check-changelog-fragments.sh passes.
  • The PR body asks for a host rerun of interview-closing-probe-something-else (3 runs, opus judge); the case reaching a with-arm score of 0.8 or more in a VALID run is that rerun's check, not this slice's gate.
Lingua principale
Shell
Stelle
22
Fork
2
Merge medio
1h 38m
PR unite (30g)
911

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di melodic-software/claude-code-plugins

Tutte le issue di melodic-software/claude-code-plugins

Issue simili

Altre issue su Shell/Bash

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.