Skip to content

List enforcement-placing skills and give each one route to the ladder #15729

Open
0 of 2 issues completed
Open

Description

@kyle-sexton

Parent

Refs #15703
Source: PLAN Phase 13, topic ecosystem-specifics

Depends on

Outcome

Every existing skill and agent that recommends, places or builds enforcement or an instruction is listed with a keep or change call, and the ladder's Selection rules table and carrier copies match that list in one ladder minor. The per-plugin skill-text changes are filed from the list as follow-on items.

Demo: the pull request body holds the list with one call per skill, and the shared-copy sync check passes after the ladder minor.

Steps:

  • List candidates by searching skill bodies and agent definitions for hook, lint rule, analyzer, instruction-file and enforcement terms, then read each hit against the scope test: does it recommend, place or build enforcement or an instruction? Record the list with a keep or change call per skill in the pull request body.
  • A listed skill with no ladder copy is to call /corrections:codify, presence-gated, with the two-sentence strongest-first fallback. A skill that applies its own selection rule keeps or gains a synced copy and a row in the ladder's Selection rules table.
  • The three carriers that hold a ladder copy with no Selection rules row today (review, session-flow, architecture) each get the same call: a row, or the copy removed and a call to codify.
  • All Selection rules rows and copy removals land in this item as one ladder minor: one regeneration, one changelog fragment per carrier.
  • File one follow-on item per plugin whose skill text changes, under the same container, each with its run budget: that skill's cases on the opus and sonnet aliases, three runs per side, and no more than 240 runs per plugin. State the number of follow-on items before filing them.

Decisions

  • D4 (AC12): added by the plan from the design's module layout and interview Q14, and approved by the owner with the plan.
  • Design Q21: a skill that carries no ladder copy reads the ladder by calling codify; only a skill that applies its own selection rule holds a synced copy and a Selection rules row.
  • The Selection rules edit lands after the inventory item merges, since it regenerates the copy that item's plugin holds.

Key interfaces

  • "A skill that carries no ladder copy calls /corrections:codify, presence-gated, with a two-sentence strongest-first fallback. Only a skill that applies its own selection rule holds a synced copy and gets a row in the ladder's Selection rules table."
  • Conventions followed: the plugin philosophy rule that a cross-plugin reach is a presence-gated slash reference; the ladder's version rule.

Done when

  • AC12 (list and ladder half): every existing skill that recommends, places or builds enforcement or an instruction is on the recorded list with its route: a synced ladder copy plus a Selection rules row, or a call to /corrections:codify.
  • Every skill routed to a synced copy is named in the ladder's Selection rules table, and the shared-copy sync check passes.
  • The follow-on items for the skill-text changes exist under the container, and their count is stated on this item.
  • The pull request body names this repository's dogfooding step.
  • AC7: nothing is cut here, so no control result is owed.
  • AC10: no new enforcement-placing skill is added here.

Out of scope

  • The per-plugin skill-text changes themselves (follow-on items).
  • Renaming rungs or moving tiers.

Activity

  1. added
    agent-readyFully specified and briefed; eligible for autonomous pickup from the frontier.
    on Nov 12, 2026
  2. added theissue type on Nov 12, 2026
  3. github-actions commented on Nov 13, 2026

    @github-actions
    Contributor

    Size: Large
    Complexity: Medium
    Uncertainty: Knowable
    Flags: none
    Blocked by: #15706, #15708, #15711

    Understood: inventory every skill and agent that recommends, places or builds enforcement or an instruction. Give each a keep or change call, routed either to a synced ladder copy with a Selection rules row or to a presence-gated /corrections:codify call. Land all ladder changes as one minor, then file one follow-on item per plugin whose skill text changes. The outcome, steps and done-when items are exact, so no owner question is open.

    The issue lists #15706, #15708 and #15711 as dependencies, and all three are still open. The Selection rules edit has to wait for them. The work is large because it spans many plugins and a count of follow-on items has to be stated. I found no duplicate or merged fix.

    Automated triage. A maintainer reviews it.

  4. melodic-automation-lanes commented on Nov 13, 2026

    @melodic-automation-lanes
    Contributor

    Not admitted to the issue lane yet: Size large: the split into sub-issues at intake is pending (owner Q93).

  5. melodic-automation-lanes commented on Nov 13, 2026

    @melodic-automation-lanes
    Contributor

    Split at intake (owner Q93). This issue is Size Large, so its done-when is split into 2 sub-issues, each holding its task-list lines as written.

    Automated split by the lanes App. Admission waits on this issue while a sub-issue is open; work-unblock closes it as completed once every sub-issue is closed as completed by a merge or a listed human and its done-when is covered.

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

    agent-readyFully specified and briefed; eligible for autonomous pickup from the frontier.

    Type

    Fields

    Work status

    ready

    Priority

    medium

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions