Skip to content

pm-dispatch SKILL structural compression: 3050 → ~1400–1600 lines (PR₂ of batch #7631, maintainer-directed) #7754

Description

@os-help

Handoff card filed by the skills seat (#7623, session session_01ATJiqhFNL82YwV8udPkoqX) — the session ran out of budget mid-batch and the maintainer directed the remainder be filed for another seat to pick up. This is PR₂ of batch #7631; PR₁ (the eight ruled amendments) merged at 2026-08-11 11:45Z as PR #7698, so this card is unblocked and dispatchable now.

Maintainer directive (verbatim, untranslated — skills seat 专题讨论, 2026-08-11)

> 现在 的 项目经理skills 太长了,需要考虑怎么压缩

Delivery shape (PR₁ then PR₂, pure moves last) was accepted in the same exchange and is recorded on #7631.

Measured starting state (origin/main after PR #7698 — re-measure at work time, do not trust these)

.claude/skills/pm-dispatch/SKILL.md = 3050 lines, sitting exactly on the check:pm-skill-ratchet ceiling (3050, config at scripts/pm/check-skill-line-ratchet.mjs). references/incidents.md = 437 lines (append-only). references/compile-surfaces.md = 27.

Composition measured before PR₁ (shape still holds; re-derive the numbers):

section lines
The round loop 1870 — step 5 Dispatch 587 (Prompt template 326), step 7 Review 380, step 0 sweep 200, step 6 Collect 195, 入队与落地 167, step 8 130
Operational notes 612 (21 notes, each = rule + incident narrative)
Domain lanes 209 (incl. the spec-tooling 沿革 111, self-labelled "沿革, 不是待办")
State model / Epic / Guardrails / report contract ~300, mostly load-bearing

Target and method

  • Target ~1400–1600 lines in the main file (roughly −50%).
  • Every rule keeps three things in the main file: the imperative, its criteria/command, and a one-line case anchor (issue number). Narratives, 沿革, worked examples and incident retellings move verbatim to references/incidents.md (append-only, one 出处 line per section, matching the convention PR pm-dispatch SKILL batch: eight ruled amendments — four-lens block, ADR-class skills, three-query board, queue criteria, five shift lessons, claim spelling, seat-post bounds, dispatch-contract rank (#7631) #7698 established with 24 such moves) or a new references/operational-notes.md if the notes section warrants its own file.
  • Machine-consumed content stays: domain-lane table, 词表 roster, seat/label setup loop, the escalation frame (all four gate-synchronized copies — check:skill-frame-sync), report contract JSON.
  • No rule deletion. Compression moves prose; removing a binding rule, criterion, or prohibition requires its own maintainer ruling. A reviewer must be able to diff old→new and see every imperative still present.
  • Ratchet: lower the ceiling to the achieved count (shrink-only lock-in) in the same PR.

Constraints

Prior art to reuse

PR #7698's diff is the pattern: each moved section left an anchor + pointer in place and gained an 出处 line at the destination. The cloud dev session that did PR₁ (session_01KCFsFypEHm1Cnp26yAofxg, now archived) sketched this plan in its report's open_questions[2] on #7631.

Activity

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

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions