Skip to content

docs(planning): point draft-goal-condition's ultracode lines at the docs without losing behavior offline #12357

Description

@kyle-sexton

This was generated by AI.

Parent

Sliced from #11823 (findings 1 and 2; see #12272's "Remaining on #11823").

Problem

plugins/planning/skills/draft-goal-condition/SKILL.md restates two volatile upstream facts:

#12272 measured cutting both to pointers. The cut showed a loss, so it was left out: the skill could not read the pointers with network access denied.

Done when

  • The two lines become pointers the skill can still act on with network access denied (for example a local record the skill reads), or the eval case runs with docs access. Either way, the eval case exercises the changed lines; plugins/planning/evals/dg-workflow-keyword-unattended (from fix(discovery,planning): point setup's fork default at the docs and add two eval cases #12272) is the existing one.
  • Before and after are measured on VALID runs (run-validity.py), with a negative control per /playbooks:skill-authoring's rewrite-a-plugin reference. The change ships only on no loss; a loss is recorded here.
  • Each shipped pointer carries an as-of date and a recheck trigger (.claude/rules/skill-bodies-state-current-rules.md).

Related

Activity

  1. added
    host-runNeeds an agent run or builder session on a host; not a person or the issue lane.
    on Nov 2, 2026
  2. added
    needs-triageNot yet classified. Floor until a type and one priority tier are set.
    on Nov 2, 2026
  3. github-actions commented on Nov 2, 2026

    @github-actions
    Contributor

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

    Size: Small
    Complexity: Medium
    Uncertainty: Knowable
    Flags: none
    Blocked by: none

    Understood: two restated upstream facts in the draft-goal-condition skill (where the ultracode keyword works, and plan availability and the xhigh condition) should become pointers that still work with network access denied. The change ships only if before and after measurements on valid runs show no loss, and each pointer carries an as-of date and a recheck trigger.

    Nothing is missing. The choice between a local record the skill reads and running the eval case with docs access is an implementation choice. I would suggest the local record, since the skill must still act offline. The measured runs may need a host or paid eval, which admission can route separately. No duplicates found among the open issues.

    Automated triage, applied by the lanes App.

  4. 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 Nov 2, 2026
  5. 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.
    on Nov 2, 2026
  6. added
    status: confirmedA maintainer confirmed the item is real and in scope; ready to be worked.
    and removed
    status: readyTriaged, unblocked, and fully specified; eligible to pick up.
    on Nov 2, 2026
  7. melodic-automation-lanes commented on Nov 2, 2026

    @melodic-automation-lanes
    Contributor

    Not admitted to the issue lane: it carries host-run. Admission takes the issue once each of those is met, when intake triages it again (.github/actions/resolve-config/admission-rules.json).

  8. melodic-automation-lanes commented on Nov 2, 2026

    @melodic-automation-lanes
    Contributor

    The latest triage verdict holds nothing: admission moved the issue to status: confirmed; its comment says why.

  9. kyle-sexton commented on Nov 2, 2026

    @kyle-sexton
    MemberAuthor

    Claimed by lane 1 (melo-lap-001, hub assignment 2026-11-02 16:5xZ). Plan: local pointer record the skill reads offline, before/after on VALID runs with a negative control via plugins/planning/evals/dg-workflow-keyword-unattended. Ships only on no loss.

  10. kyle-sexton commented on Nov 2, 2026

    @kyle-sexton
    MemberAuthor

    Lane 1: PR #12426 merged (2ab3443). It ships the keyword and plan-availability moves into reference/workflow-row.md, measured with no loss and network access denied (before 1/1/1, after 1/1/1, negative control 0.44). The xhigh clause stays in SKILL.md, now with a pointer, an as-of date and a recheck trigger. Moving it failed preregistered measurement v5: three correct answers failed the line-based grader, so the xhigh case read 0.70 against 1.00. Remaining on this issue: move the xhigh clause once #12467 makes the graders read answers that span lines, then measure again. Lane 1 releases its claim.

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

    host-runNeeds an agent run or builder session on a host; not a person or the issue lane.priority: lowNice-to-have, cosmetic, or speculative; opportunistic.status: confirmedA maintainer confirmed the item is real and in scope; ready to be worked.work-class: scopedA briefed fix or small feature; blast radius bounded by the brief, tests exist.

    Type

    Fields

    Work status

    confirmed

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions