Skip to content

decision: organization procedures live once, as public runbooks that thin skills route to #668

Description

@ss-o

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 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:

Proposal

Draft ADR-0032 (PROPOSED):

  1. Organization procedures are public and live once, as runbooks. The private maintainer workspace holds only environment bindings.
  2. 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.
  3. Few skills with strong triggers. This adopts chore(skills): remove git-commit and gh-cli, which only restate AGENTS.md policy #623 (remove git-commit and gh-cli).
  4. Anything checkable before merge becomes a check.
  5. Runtime-private skills hold runtime mechanics only.
  6. 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.

Activity

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

    area:metaOrganization-wide policy, templates, or meta-repo work.type:maintenanceNon-feature maintenance, cleanup, or org work.

    Type

    No type

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions