Skip to content

feat(planning): every /planning:interview recommendation shows its evidence, not bare judgment #6728

Description

@kyle-sexton

Problem

/planning:interview allows Basis: judgment on a non-consequential recommendation ("When no codebase signal exists, a non-consequential question may be recommended from conventions, labeled Basis: judgment", skills/interview/SKILL.md "Recommended answers"). In practice that lets a recommendation arrive with no facts behind it, and the operator cannot see why it fits them.

Requested behavior

Every recommendation carries the facts it rests on and how they combine:

  • each fact with its source: a file:line, a URL fetched this session, a session-transcript finding, or tool output
  • one line on why those facts together lead to this answer for this user
  • when only judgment is available, research before asking, or ask with the recommendation withheld and name the evidence that would settle it (the existing Withheld: shape)

Acceptance criteria

  • Basis: judgment alone is no longer a valid basis for an interview recommendation
  • The per-question shape in SKILL.md and context/recommendation-basis.md shows an evidence list plus a one-line inference
  • The page surface's basis field carries the same evidence list

🤖 Generated with Claude Code

https://claude.ai/code/session_01LGDKQK7XJf6kz6EZDzbKwM

Activity

  1. added
    needs-triageNot yet classified. Floor until a type and one priority tier are set.
    on Oct 10, 2026
  2. github-actions commented on Oct 10, 2026

    @github-actions
    Contributor

    Thanks for the report. Automated triage handed this issue to a maintainer.

    Automated triage. A maintainer reviews it.

  3. added
    needs-humanHuman-in-the-loop required; autonomous sessions must not resolve items carrying this.
    on Oct 10, 2026
  4. kyle-sexton commented on Oct 11, 2026

    @kyle-sexton
    ContributorAuthor

    Handoff note for whoever picks this up next. The overnight Claude run has stopped, and Kyle is moving issue work to Cursor.

    Where a branch is listed it is pushed, so it can be taken over as is. A draft PR shows a red ci-status by design until it is marked ready.


    Generated by Claude Code

  5. removed
    needs-triageNot yet classified. Floor until a type and one priority tier are set.
    on Oct 12, 2026
  6. kyle-sexton commented on Oct 13, 2026

    @kyle-sexton
    ContributorAuthor

    Decision recorded. The owner approved applying independently verified recommendations on 2026-10-12.

    • Drop Basis: judgment as a valid interview basis, replacing it with an evidence list plus a one-line inference? → Yes, as the issue asks
      Basis: plugins/planning/skills/interview/SKILL.md:175 (current judgment allowance); plugins/planning/skills/interview/context/loop.md:67 (Withheld: line); AGENTS.md Team standards (judgment allowed)
    • Can the Stance-section digest in interview-defenses.test.sh be recomputed in an attended session for this change? → Yes, attended recompute
      Basis: fix(planning): word interview questions so yes accepts the recommendation #7036 body ("none of the six with-arm traces read it"; maintainer approved recomputing the digest, attended, 2026-10-11)
    • Drop Basis: judgment as a valid interview basis? → Yes for /planning:interview only: tighten SKILL.md:175 and loop.md:67 to an evidence list plus a one-line inference, and leave the shared context/recommendation-basis.md unchanged. Changing the shared contract is a separate cross-plugin convention decision. (added by verification)
      Basis: scripts/cross-plugin-source-registry.txt:116-121; plugins/planning/context/recommendation-basis.md:25-31; md5 identical across planning/debugging/work-items copies (origin/main)
    • Digest recompute scope → Attended recompute of both the SKILL.md Stance digest and the loop.md Step 2 digest. (added by verification)
      Basis: plugins/planning/tests/interview-defenses.test.sh:498-502 and :634 (origin/main)

    The owner asks that interview recommendations always list their facts and a one-line inference, ending bare Basis: judgment. No PR; the 2026-10-11 handoff skipped it for lack of a recorded decision, and the rule sits in the digest-pinned Stance section that #7036 also edited.

    Verification notes:

    • Q1 'Yes, as the issue asks' includes the issue's acceptance criterion to change context/recommendation-basis.md. That file is a synced cross-plugin copy (13 plugins ship it, byte-identical; canonical plugins/discipline/context/recommendation-basis.md; drift-checked via scripts/cross-plugin-source-registry.txt:116-121), and its three outcomes include judgment (lines 25-31), matching the org convention and team standards. Editing planning's copy fails the drift check; editing the canonical changes 13 plugins' contract, which is cross-plugin, not C3. The record's own 'why' (a stricter interview rule does not contradict the floor) only holds if the change stays in interview files.
    • Q2 names only the Stance digest. loop.md:67 (Frontier rounds, item 4, which also permits Basis: judgment) sits inside the pinned 'loop.md Step 2 section' (interview-defenses.test.sh:634), so that digest needs an attended recompute too.
    • SKILL.md:175 is inside the pinned Stance section (SKILL.md:90 to 315; test.sh:498-502), as the record says.

    Verified by an independent fresh-context check (refuted, risk low): gh issue view 6728 (handoff 2026-10-11: skipped, no owner decision); plugins/planning/skills/interview/SKILL.md:170-178 and section headings; plugins/planning/skills/interview/context/loop.md:62-70 and headings; plugins/planning/context/recommendation-basis.md; scripts/cross-plugin-source-registry.txt:116-121; plugins/planning/tests/interview-defenses.test.sh pin_section list

    Admission to an agent lane stays with the work-class rules and owner ratification.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    needs-humanHuman-in-the-loop required; autonomous sessions must not resolve items carrying this.

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions