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
decision: organization procedures live once, as public runbooks that thin skills route to #668
Organization tasks (triaging an issue, taking a pull request from branch to merge, updating Project 28) run differently depending on the agent runtime and the repository, so outcomes vary and lessons have nowhere shared to land.
The procedures mostly exist, as runbooks (triage.md, project-tracker.md, release.md, org-review.md, learning-capture.md, and more). But none of the ten skills here covers triage, pull requests, the tracker, or releases, and only code-review and zi-install are vendored downstream (lib/approved-skills.json).
A review of one agent session working through the z-shell/zsh-lint backlog on 2026-09-26 found:
The agent worked from runtime-private skills that restated rules from this repository (the ADR-0026 fallback, branch names, the issue form, tracker fields). Those copies had drifted, and context compaction pruned them mid-session.
Its runtime did not load the organization skills at all: project skills needed a per-worktree trust step that had not been taken.
The outcomes that varied were exactly the unwritten ones:
Rules enforced before the pull request opened, such as the issue link and PR title, were followed.
Proposal
Draft ADR-0032 (PROPOSED):
Organization procedures are public and live once, as runbooks. The private maintainer workspace holds only environment bindings.
An organization skill is a thin router: trigger-rich description, checklist, gates and checks, then "read the runbook". This is the pattern review-project-learning already follows.
Runtime-private skills hold runtime mechanics only.
Delivery is verified per runtime.
Follow-ups (after the ADR)
runbooks/pull-requests.md: branch naming, Closes only when every acceptance criterion is met, the review gate and ADR-0026 fallback executed under code-review, a push voiding an earlier review, merge, post-merge. Depends on decision: amend ADR-0026 for maintainer-elected fallback reviews #664; the maintainer's position there is to allow a maintainer-elected fallback with its own marker, still running the checklist.
An investigation and evidence standard for triage.md, and a duplicate search that covers closed issues.
Thin issue-triage, pull-request and project-tracker skills, then delivery and reference-integrity checks.
Problem
Organization tasks (triaging an issue, taking a pull request from branch to merge, updating Project 28) run differently depending on the agent runtime and the repository, so outcomes vary and lessons have nowhere shared to land.
The procedures mostly exist, as runbooks (
triage.md,project-tracker.md,release.md,org-review.md,learning-capture.md, and more). But none of the ten skills here covers triage, pull requests, the tracker, or releases, and onlycode-reviewandzi-installare vendored downstream (lib/approved-skills.json).A review of one agent session working through the z-shell/zsh-lint backlog on 2026-09-26 found:
Closes #470although it met only part of ci(labels): run the labels-sync test suite on tooling changes #470's acceptance criteria (follow-up Promote F-Sy-H to the strict corpus and correct the regression-corpus survey record zsh-lint#488);code-reviewchecklist having run;docs-488failed the required branch-name check (docs(corpus): verify the Zsh 5.9 false accepts in the regression survey record (#488) zsh-lint#490, reopened as fix(ci): stop profile deploys overwriting wiki #491). The rule existed, but only in CI, where the agent first met it.Proposal
Draft ADR-0032 (PROPOSED):
review-project-learningalready follows.git-commitandgh-cli).Follow-ups (after the ADR)
runbooks/pull-requests.md: branch naming,Closesonly when every acceptance criterion is met, the review gate and ADR-0026 fallback executed undercode-review, a push voiding an earlier review, merge, post-merge. Depends on decision: amend ADR-0026 for maintainer-elected fallback reviews #664; the maintainer's position there is to allow a maintainer-elected fallback with its own marker, still running the checklist.triage.md, and a duplicate search that covers closed issues.issue-triage,pull-requestandproject-trackerskills, then delivery and reference-integrity checks.