You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Part of #6476. Rewrite harness-config'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.
Proposed work class: work-class: structural
Basis: automated intake triage; the lanes App applied this class.
Size: Large
Complexity: Medium
Uncertainty: Known
Flags: none
Blocked by: none
Understood: this is the harness-config part of the concise-skills rollout (#6476). It rewrites the plugin's 10 skills to the skill criteria, following the per-plugin runbook. The latest comment says the owner rules already cover the eval spend, so no cost decision is open. The work is too big for one change. It should be split into sub-issues, with outcome eval cases first and then rewrite slices of a few skills each, as that comment's criteria describe. I found no likely duplicates among the open issues.
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:
The issue is split into sub-issues with blocked-by edges before any run (Q93/Q94): outcome eval cases for harness-config first, then rewrite slices of a few skills each.
Each rewrite slice's PR carries a per-skill decision table, and every shipped description or body change is backed by a valid measured pass on the subscription.
Any skill left unmeasured is named in its PR with the reason.
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 by a merge or a listed human.
Activity
github-actions commentedon Oct 7, 2026
Proposed work class: work-class: structural
Basis: automated intake triage; the lanes App applied this class.
Size: Large
Complexity: Medium
Uncertainty: Known
Flags: none
Blocked by: none
Understood: this is the harness-config part of the concise-skills rollout (#6476). It rewrites the plugin's 10 skills to the skill criteria, following the per-plugin runbook. The latest comment says the owner rules already cover the eval spend, so no cost decision is open. The work is too big for one change. It should be split into sub-issues, with outcome eval cases first and then rewrite slices of a few skills each, as that comment's criteria describe. I found no likely duplicates among the open issues.
Automated triage, applied by the lanes App.
kyle-sexton commentedon Oct 22, 2026
Parked (owner decision 2026-10-21): no eval spend until #7719 resumes hardening. This stays open and resumes then.
3 remaining items
kyle-sexton commentedon Oct 26, 2026
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:
github-actions commentedon Oct 26, 2026
The triage sweep dispatched intake triage for this issue (attempt 1 of 2).
melodic-automation-lanes commentedon Oct 26, 2026
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 by a merge or a listed human.
melodic-automation-lanes commentedon Nov 2, 2026
Every sub-issue of this split is closed as completed by a listed human or a merge (#10221, #10222, #11560, #11561, #11563, #11564, #11565, #11566), so the lanes App closes it as completed.