feat(agents): pm-dispatch 首轮实跑经验回写 — 认领协议、跨仓查重、决策落原 issue、开发模型策略 - #4554
Merged
Conversation
…o dedup, escalate-on-issue, dev model policy Four mechanics hardened from the first live dispatch round: - Claim protocol: shared GitHub identity means assignee alone cannot say WHICH agent claimed — a fixed-shape claim comment (round + branch name) carries identity, a comment read-back settles races (first comment wins), early branch push closes the claimed-but-invisible gap, and stale claims (24h, no branch, no PR) are reclaimed after inquiry. - Cross-repo dedup at triage: follow cross-references and keyword-search sibling repos for an issue's shadow; claimed shadow blocks dispatch, unclaimed shadow converges to one entry first, done shadow triggers a staleness check. The main backlog stays the only scheduling authority. - Escalation lands ON the issue it belongs to (analysis comment + needs-user-decision label as the maintainer's inbox); a separate [decision] issue only when no natural anchor exists — decision cards no longer accumulate. - Dev dispatches pass model: opus; the PM session keeps the stronger orchestration model (maintainer policy). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_012C2cd7tL8QDoZ2QKN3djJ5
|
The latest updates on your projects. Learn more about Vercel for GitHub. 1 Skipped Deployment
|
github-actions
Bot
added
documentation
…s land via the merge queue Maintainer policy: once the PM's review verdict is ACCEPT and every CI check is green, the PM marks the dev-agent PR ready and adds it to the merge queue (the repo's sanctioned path — the queue lands it only if the rebuild against current main is green). Scope-limited: dev-agent PRs dispatched by this loop only; the PM's own tooling PRs stay with the maintainer; no red, unreviewed, or queue-bypassing merges. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_012C2cd7tL8QDoZ2QKN3djJ5
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
目的
/pm-dispatch第一轮真实派发(#4551、#4518 已派发;#4515、#4525 已转决策)暴露的四处机制空白,连同维护者的三条反馈,回写进 skill。内容(均为
.claude/skills/pm-dispatch/SKILL.md)1. 认领协议(step 4 重写)。 所有 agent 共用一个 GitHub 账号,assignee 只能表达「有人认领」而非「谁认领」:
2. 分诊时跨仓查重(step 2 新增)。 派发前顺着 issue 的跨仓引用 + 关键词搜索另两个仓库找「影子」:影子已认领/有 PR → 不派发写
Blocked-by:;影子未认领 → 先收敛成单一调度入口再入队;影子已完成 → 复核原 issue 是否过时。主 backlog 是唯一调度权威。3. 决策落在原 issue 上(step 8 重写,回应维护者「[决策] issue 会不会越来越多」)。 默认把两轴分析评论到所属 issue 并打
needs-user-decision——该标签就是维护者的收件箱,拍板后摘标即回队列,不产生记账 issue;仅当决策没有天然归属(横跨多 issue / 凭空冒出)才单独建[决策]issue。4. 开发模型策略(step 5,维护者指定)。 派发开发 agent 一律传
model: "opus";PM 会话保持更强的编排模型,把判断力花在分诊、复核与决策框架上。备注
.claude/内部工具,不发布任何 package)。isSystem写入仍可产生悬空 lookup 引用——需要一条只报告不拦截的巡检（#4441 残留） #4551、[verify]bootStack({ databaseFile })的数据活不过进程内重启 —— 表在、行没了，挡住冷启动类 e2e #4518 已按新认领协议认领并以 Opus 派发中;[automation] getSuspendedScreen 只读内存热缓存 —— 重启后一个仍然活着的挂起 run 取不到它的 screen（404） #4515、spec 是否该建模DecisionOutputDef.required？服务端今天就在强制它，而 spec 未声明 #4525 已按新升级路径评论分析并打needs-user-decision。🤖 Generated with Claude Code
https://claude.ai/code/session_012C2cd7tL8QDoZ2QKN3djJ5
Generated by Claude Code