Skip to content

docs(planning): finish continuation wording in digest-pinned interview sections #7425

Open

Description

@kyle-sexton

Follow-up from PR #7417 (#5811). Review found four wording fixes inside sections whose text plugins/planning/tests/interview-defenses.test.sh pins by digest; recomputing a digest is attended-only, so they were left out of #7417.

  • plugins/planning/skills/interview/context/loop.md:161: stale cross-reference to "the handoff-and-clear in 'Incremental persistence + branch-out'", which no longer exists.
  • plugins/planning/skills/interview/SKILL.md:403: "incremental-persistence and handoff discipline" should read "continuation discipline".
  • SKILL.md:420: the me-mode route line has no fallback without session-flow; suggested "(if installed; otherwise Step 5's fallback)".
  • SKILL.md:420 and loop.md:211: "Route the next step" should read "Recommend routing the next step".

Acceptance: the edits land and an attended session re-pins the SKILL.md Step 4 and loop.md relentless-section digests; interview-defenses.test.sh passes.

Done when

Line numbers in the list above are stale; on main at 2f6b81e the passages are at context/loop.md:261 and SKILL.md:417 and :434.

  • git grep -n 'handoff-and-clear in "Incremental persistence' -- plugins/planning/skills/interview/ prints nothing.
  • git grep -n 'incremental-persistence and handoff discipline' -- plugins/planning/skills/interview/SKILL.md prints nothing, and git grep -n 'continuation discipline' -- plugins/planning/skills/interview/SKILL.md prints a line.
  • git grep -n 'Route the next step' -- plugins/planning/skills/interview/ prints nothing.
  • The me-mode route line names a fallback when session-flow is absent: git grep -n "otherwise Step 5's fallback" -- plugins/planning/skills/interview/SKILL.md prints a line.
  • The loop.md docs link carries a Pointer / As of / Recheck trigger record.
  • The SKILL.md and loop.md digests are re-pinned and scripts/run-test-file.sh plugins/planning/tests/interview-defenses.test.sh passes.
  • scripts/check-changelog-fragments.sh passes.

Activity

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

    @github-actions
    Contributor

    Proposed work class: work-class: scoped
    Basis: automated intake triage; the lanes App applied this class.

    Size: Small
    Complexity: Low
    Uncertainty: Known
    Flags: none

    Understood: four wording fixes and one Pointer / As of / Recheck record in the planning interview skill (SKILL.md and context/loop.md). Both files sit in digest-pinned sections, so the digests must be re-pinned and interview-defenses.test.sh must pass. The done-when list gives exact git-grep checks. The issue says the line numbers are stale and gives current ones. The owner's comment says the issue is released. No likely duplicates found in the open issues.

    Automated triage, applied by the lanes App.

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

    @kyle-sexton
    MemberAuthor

    Also from #7417 (Codex): plugins/planning/skills/interview/context/loop.md:211 docs link needs the labeled Pointer / As of / Recheck trigger record; it sits inside the digest-pinned relentless section.

  5. added theissue type on Oct 15, 2026
  6. added
    priority: lowNice-to-have, cosmetic, or speculative; opportunistic.
    and removed
    needs-triageNot yet classified. Floor until a type and one priority tier are set.
    on Oct 15, 2026
  7. removed
    needs-humanHuman-in-the-loop required; autonomous sessions must not resolve items carrying this.
    on Oct 24, 2026
  8. kyle-sexton commented on Oct 24, 2026

    @kyle-sexton
    MemberAuthor

    Released by the owner's HITL session (2026-10-24, C12): it waited only on a removed gate. Intake triage re-runs on it to set its fields, then admission takes it.

  9. added
    status: readyTriaged, unblocked, and fully specified; eligible to pick up.
    work-class: scopedA briefed fix or small feature; blast radius bounded by the brief, tests exist.
    agent-readyFully specified and briefed; eligible for autonomous pickup from the frontier.
    on Oct 24, 2026
  10. melodic-automation-lanes commented on Oct 24, 2026

    @melodic-automation-lanes
    Contributor

    The work-resolve-issue run that agent-ready started failed or was cancelled before it reported, or it stopped or the token broker refused it because its workflow files differ from main's. work-unblock removed and added agent-ready back to start a fresh run on main's workflow files. It does this once per version of those files, so if this run fails the same way, a person looks at it.

  11. added
    agent-readyFully specified and briefed; eligible for autonomous pickup from the frontier.
    needs-humanHuman-in-the-loop required; autonomous sessions must not resolve items carrying this.
    and removed
    agent-readyFully specified and briefed; eligible for autonomous pickup from the frontier.
    on Oct 24, 2026
  12. melodic-automation-lanes commented on Oct 24, 2026

    @melodic-automation-lanes
    Contributor

    The work-resolve-issue lane stopped partway through this issue and needs a person.

    Why, in the run's own words:

    The issue's acceptance requires re-pinning the SKILL.md Step 4 and loop.md relentless-section digests in plugins/planning/tests/interview-defenses.test.sh. That file states, and plugins/planning/CHANGELOG.md records (#5332), that recomputing a digest or pin is attended-only: an unattended run reports the pin and diff, then stops. Every edit the issue lists lands inside a digested region, so making the wording edits here would leave interview-defenses.test.sh failing, and re-pinning from this CI run is forbidden. No files were changed.

    What the run says it did not do:

    • The four wording edits (loop.md stale handoff-and-clear cross-reference; SKILL.md 'continuation discipline'; me-mode route fallback '(if installed; otherwise Step 5's fallback)'; 'Recommend routing the next step' in SKILL.md and loop.md) and the loop.md docs link Pointer / As of / Recheck trigger re
    • Re-pin of the SKILL.md Step 4 / Step 1.5 and loop.md relentless-section digests (bash plugins/planning/tests/repin.sh) and a passing run of interview-defenses.test.sh were not done: attended-only.

    Run: https://github.com/melodic-software/claude-code-plugins/actions/runs/40136024505

    To retry, remove needs-human and add agent-ready again.

  13. kyle-sexton commented on Oct 26, 2026

    @kyle-sexton
    MemberAuthor

    This was generated by AI.

    Routed to the host runner, not the owner. The wording edits sit inside digest-pinned sections, and plugins/planning/tests/repin.sh writes only from a terminal (https://github.com/melodic-software/claude-code-plugins/actions/runs/40136024505). Attended work is agent work now, so this goes with #6728: the host session replaces the terminal-only re-pin with one an independent fresh-context check confirms, in a pull request, then lands these edits.

    Under the owner's 2026-10-26 stop rule, a person is needed only for a change in intent or vision, an implementation finding that changes the intent or primary design, or a high or critical security issue; host, attended and eval runs are agent work. So needs-human comes off. It moves to the host-run label, and the host runner takes it.

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.priority: lowNice-to-have, cosmetic, or speculative; opportunistic.status: readyTriaged, unblocked, and fully specified; eligible to pick up.work-class: scopedA briefed fix or small feature; blast radius bounded by the brief, tests exist.

    Type

    Fields

    No fields configured for Task.

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions