Skip to content

Concise skills rollout: docs-hygiene (10 skills, 9 model-invoked) #6554

Open

Description

@kyle-sexton

Part of #6476. Rewrite docs-hygiene's skills to the skill criteria in one draft PR, following the per-plugin runbook (/playbooks:skill-authoring, reference/rewrite-a-plugin.md). The runbook and the rewrite protocol it cites decide what ships; this issue holds only what is specific to the plugin.

The plugin today

  • Skills: audit-derivability, audit-encapsulation, audit-noise, audit-progressive-disclosure, compress, extract-ssot, rename-references, setup (user-invoked), write-for-agents, write-for-humans.
  • Outcome eval cases under evals/: 4. Probe files under probes/: 0.
  • 1 agent definition(s): out of scope for this skills pass unless the umbrella's agent pilot has landed.

Done when

  • The PR merges with a per-skill decision table in its body, and every shipped description and body was measured.
  • Any skill left unmeasured, and why, is named in the PR.

Needs a person

  • Approve the eval spend for this plugin (the /evals:plugin-eval estimate) before the measured passes.
  • Review the draft PR and mark it ready.

Generated by Claude Code

Activity

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

    @github-actions
    Contributor

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

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

    Understood: one draft PR that rewrites the ten docs-hygiene skills to the skill criteria, following the playbooks rewrite-a-plugin runbook. It needs a per-skill decision table, and every shipped description and body change needs a measured eval pass. Any unmeasured skill gets named in the PR with its reason. The agent definition stays unchanged unless the #6476 agent pilot has landed.

    Nothing is missing, and I found no likely duplicates. The eval runs use the subscription login. They can't run in the issue lane, so an eval session has to run them.

    Automated triage, applied by the lanes App.

  3. removed
    needs-triageNot yet classified. Floor until a type and one priority tier are set.
    on Oct 12, 2026
  4. added theissue type on Oct 12, 2026
  5. added
    needs-humanHuman-in-the-loop required; autonomous sessions must not resolve items carrying this.
    on Oct 19, 2026
  6. kyle-sexton commented on Oct 19, 2026

    @kyle-sexton
    MemberAuthor

    This was generated by AI during triage.

    Hold: the owner decision on #6476 (2026-10-18) puts this plugin in batch 2, which runs in a dedicated attended eval session, two plugins at a time, under a per-pass cost ceiling. It is not work for an unattended lane.

  7. kyle-sexton commented on Oct 22, 2026

    @kyle-sexton
    MemberAuthor

    Parked (owner decision 2026-10-21): no eval spend until #7719 resumes hardening. This stays open and resumes then.

  8. removed
    needs-humanHuman-in-the-loop required; autonomous sessions must not resolve items carrying this.
    on Oct 25, 2026
  9. added
    needs-triageNot yet classified. Floor until a type and one priority tier are set.
    and removed
    needs-triageNot yet classified. Floor until a type and one priority tier are set.
    on Oct 25, 2026
  10. 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.
    status: needs-decisionAwaiting a human or maintainer judgment call.
    on Oct 25, 2026
  11. melodic-automation-lanes commented on Oct 25, 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).

  12. melodic-automation-lanes commented on Oct 25, 2026

    @melodic-automation-lanes
    Contributor

    The latest triage verdict holds nothing: the issue is at status: ready.

  13. melodic-automation-lanes commented on Oct 25, 2026

    @melodic-automation-lanes
    Contributor

    Refinement. A read-only run explored this repository, searched its issues and pull requests, and read the allowed docs to draft what follows. On an issue a listed human filed, it counts as the issue's spec once posted, while unedited; it is still model text, so check it.

    Intended outcome: All 10 docs-hygiene skills are rewritten to the skill criteria in one draft PR with a per-skill decision table and measured descriptions and bodies.

    Dependencies

    • #​6476 umbrella: batch 2 runs in an attended eval session, per its 2026-10-18 owner decision
    • #​7719: owner parked eval spend until hardening resumes (2026-10-21)

    Related work

    Open questions

    1. Should this issue stay held until #​7719 resumes hardening and the owner approves the /evals:plugin-eval spend, rather than being picked up by an unattended lane?
      RECOMMENDED: Yes, keep it parked and out of the unattended lane until both happen. Basis: Owner comments of 2026-10-19 and 2026-10-22 on this issue
    2. Should the body gain a task list of checkable criteria, such as a decision-table row per skill and named unmeasured skills, so the issue can be admitted once it is unparked?
      RECOMMENDED: Yes. Add one item per skill (10), a decision-table item and an unmeasured-skills item, and move eval-spend approval and draft-PR review into the person-only items. Basis: judgment
    3. Is the docs-hygiene agent definition in scope for this pass?
      RECOMMENDED: No. Exclude it unless the umbrella's agent pilot has landed. Basis: Issue body, 'The plugin today' section

    Sources read

    • plugins/docs-hygiene/skills/*/SKILL.md: the plugin has 10 skills (audit-derivability, audit-encapsulation, audit-noise, audit-progressive-disclosure, compress, extract-ssot, rename-references, setup, write-for-agents, write-for-humans), matching the issue body

    Automated refinement by the lanes App. Answer with a comment whose first line is **Decision recorded.**.

  14. kyle-sexton commented on Oct 25, 2026

    @kyle-sexton
    MemberAuthor

    Unparked by the owner's HITL session (2026-10-24): the owner's rule is that nothing stays parked unless it is unclear intent, a changed direction, a high security risk or an induced cost, and this hold was none of those.

    The runs use the eval lane's MAINTENANCE role (.github/lane-funding.json, role maintenance: keyed: false, MAINTENANCE_CLAUDE_CODE_OAUTH_TOKEN, a flat-fee subscription) or a local run on the operator machine's subscription; neither charges an auto-renewing key or a metered bill. The issue lane cannot run evals, so this goes to the eval session, not the lane.

  15. kyle-sexton commented on Oct 26, 2026

    @kyle-sexton
    MemberAuthor

    This was generated by AI.

    Releasing the hold: no owner question is open. The refinement asked about eval spend or who runs the eval. Owner rules settle both. Evals run on the subscription login or not at all, never with an API key, and none start while the rate limit is near (Q110). Subscription and prepaid spend are not induced cost (Q46, Q91). Under the owner's 2026-10-26 stop rule (C14), an eval or host run is no longer an owner step, so an agent session runs it. The label comes off and intake triage runs again. Criteria:

    • One PR rewrites the docs-hygiene skills to the skill criteria per plugins/playbooks/skills/skill-authoring/reference/rewrite-a-plugin.md, with a per-skill decision table in its body.
    • Every shipped description and body change is backed by a valid /evals:plugin-eval measured pass run on the subscription.
    • Any skill left unmeasured is named in the PR with its reason.
    • The agent definition is unchanged unless the Concise skills: one skill-creation standard, evals, and a fleet-wide rollout #6476 agent pilot has landed.
  16. github-actions commented on Oct 26, 2026

    @github-actions
    Contributor

    The triage sweep dispatched intake triage for this issue (attempt 1 of 2).

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

    priority: mediumReal value, no hard deadline; normal backlog flow.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