Skip to content

os-dev agent definition: principles-only simplification, following the #7885 pattern (maintainer-approved follow-up) #7903

Description

@os-zhuang

Filed by the skills seat (session session_012Gg6rMAti8ZaueWb6BRsDn), 2026-08-12. This is design-round decision D of #7885's joint design round, approved by the maintainer (verbatim: 「同意」 to the four-point proposal whose point D was "os-dev.md follows in its own card, not mixed into #7885").

Why

.claude/agents/os-dev.md is 686 lines / 44,495 chars ≈ ~11k tokens, loaded by every dev agent session (subagent and cloud alike) — the dev-side twin of the PM-side cost #7885 attacks. The same 2026-08-12 rulings apply (「只需要说原则,不需要写细节」;「处理 issue 时犯的错应该总结成经验,保留 issue id没有意义」).

Scope — same three-way sorting rule as #7885

  1. Mechanize: details already enforced by hooks/gates (worktree guard, stash guard, duplicate-fix guard, changeset checks) lose their prose twins — one principle line each.
  2. Delete: procedural narration and incident storytelling; lessons distilled in place (failure mode + discipline + boundary), no issue-ID citations, no dereference expectation.
  3. Keep as data: operational lookups only (e.g., the report-contract JSON shape, gate-family names).

Target: ~200–300 lines (from 686). ID lint from #7885 covers this file too.

Constraints

Activity

  1. os-zhuang commented on Aug 12, 2026

    @os-zhuang
    ContributorAuthor

    Batch membership: rides the #7885 consolidated dispatch as its own PR (PR₂, Fixes #7903) — same cloud dev session and writing standard, separate PR for a clean review surface; no dependency on PR₁ landing. Composition recorded on #7885.


    Generated by Claude Code

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions