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
{{ message }}
Repository navigation
Concise skills rollout: harness-config \(10 skills, 9 model-invoked\) - part 1 of 2 #10221
Part 1 of 2 of #6555, split at intake (owner Q93). The done-when below is copied from #6555 as written.
Done when
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.
Size: Medium
Complexity: Medium
Uncertainty: Knowable
Flags: none
Blocked by: none
Understood: this is part 1 of 2 of #6555, split at intake. The work is to break the harness-config concise-skills rewrite into sub-issues with blocked-by edges. Outcome eval cases come first, then rewrite slices of a few skills each. Nothing is missing. The sibling issue, part 2 of 2, is a companion rather than a duplicate. It is not a blocker as far as the issue text shows.
The work-resolve-issue lane stopped on this issue (host-only): the run reports the work needs a host run the lane cannot make.
It added host-run and removed agent-ready: an agent run on a host builds it, and it waits on no decision from a person.
In the run's words:
host-only: the issue's only done-when line is a tracker operation: split the harness-config concise-skills rollout into GitHub sub-issues joined by blocked-by edges (outcome eval cases first, then rewrite slices of a few skills each). That means creating issues and dependency edges on GitHub. This lane can only produce a working-tree patch and cannot reach the tracker, so no file change would satisfy the line. Someone needs to run /work-items:decompose (or file the sub-issues by hand) in a session that can write to the tracker.
What the run says it did not do:
Creating the sub-issues (harness-config outcome eval cases first, then rewrite slices of a few skills each) and their blocked-by edges: these are tracker writes, and this lane has no tracker access
Tidy, review, verify and checks steps were skipped because there was no change to tidy, review or verify
Cases are split per slice so each item fits one session and the three slices can run in parallel. All six carry host-run: claude plugin eval runs only on a host. setup is user-invoked and measured by semantic diff in #11565. #10222's done-when (slice PRs merge, parent closes) is unchanged.
Activity
github-actions commentedon Oct 26, 2026
Proposed work class: none
Size: Medium
Complexity: Medium
Uncertainty: Knowable
Flags: none
Blocked by: none
Understood: this is part 1 of 2 of #6555, split at intake. The work is to break the harness-config concise-skills rewrite into sub-issues with blocked-by edges. Outcome eval cases come first, then rewrite slices of a few skills each. Nothing is missing. The sibling issue, part 2 of 2, is a companion rather than a duplicate. It is not a blocker as far as the issue text shows.
Automated triage. A maintainer reviews it.
melodic-automation-lanes commentedon Oct 29, 2026
The work-resolve-issue lane stopped on this issue (
host-only): the run reports the work needs a host run the lane cannot make.It added
host-runand removedagent-ready: an agent run on a host builds it, and it waits on no decision from a person.In the run's words:
What the run says it did not do:
Run: https://github.com/melodic-software/claude-code-plugins/actions/runs/40797500241
To hand it back to the lane, remove
host-runand addagent-readyagain.kyle-sexton commentedon Oct 31, 2026
kyle-sexton commentedon Oct 31, 2026
Done: #6555 is split into sub-issues with blocked-by edges (Q93/Q94), outcome eval cases first, then rewrite slices.
Cases are split per slice so each item fits one session and the three slices can run in parallel. All six carry
host-run:claude plugin evalruns only on a host.setupis user-invoked and measured by semantic diff in #11565. #10222's done-when (slice PRs merge, parent closes) is unchanged.