easyharness

Drive an approved tracked plan through implementation, validation, independent review, archive, publish, CI/sync evidence, and readiness to wait for merge approval.

Create or update the tracked root plan and, for coordinated work, its agent-owned subplans.

Drive an approved tracked plan through implementation, validation, independent review, archive, publish, CI/sync evidence, and readiness to wait for merge approval.

Create or update the tracked root plan and, for coordinated work, its agent-owned subplans.

Clarify a harness task before planning when the objective, boundaries, tradeoffs, success criteria, or workflow direction are genuinely unclear. Do not use for factual repo questions, status checks, or approved execution.

Clarify a harness task before planning when the objective, boundaries, tradeoffs, success criteria, or workflow direction are genuinely unclear. Do not use for factual repo questions, status checks, or approved execution.

Merge an archived candidate after explicit human approval and complete required post-merge bookkeeping.

Merge an archived candidate after explicit human approval and complete required post-merge bookkeeping.

Independently review the complete candidate in an existing finalize round and submit the sole structured judgment. Use only in the reviewer subagent, never in the controller or advisor subagents.

Independently review the complete candidate in an existing finalize round and submit the sole structured judgment. Use only in the reviewer subagent, never in the controller or advisor subagents.

Proactively use after every easyharness PR lands, and when checking milestone closeout or release scope, to decide whether to recommend that the human open a patch or minor release PR. This repo-local skill is advisory only: do not bump VERSION, create release PRs, publish releases, or create release-process machinery.

Triage GitHub issues for the easyharness repository using the local backlog policy, concrete version milestones, and required rationale comments. Use when reviewing a new issue, backfilling labels on existing issues, revisiting deferred or needs-info backlog items, or deciding whether an issue should stay open, move into a concrete version milestone, or close as not planned.