backlog

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Backlog

待办事项（Backlog）

Route a backlog session to the right workflow via a short interview, then dispatch to

implement-issues

and/or

babysit-pr

. This skill decides and delegates — it implements nothing itself.

通过简短的引导对话将待办事项会话路由至合适的工作流，然后调度至

implement-issues

和/或

babysit-pr

。该Skill仅负责决策与任务委派——自身不执行任何具体实现工作。

Invocation

调用方式

```
/backlog
```
— run the interview below.
Args answer questions in advance; skip any question already answered:
- ```
/backlog merge
```
  /
```
/backlog open-pr
```
- ```
/backlog merge #124 #125
```
  — explicit PR list
- ```
/backlog open-pr #12 #14
```
  — explicit issue list

```
/backlog
```
—— 启动下方的引导对话。
通过参数提前回答问题；跳过已回答的问题：
- ```
/backlog merge
```
  /
```
/backlog open-pr
```
- ```
/backlog merge #124 #125
```
  —— 指定PR列表
- ```
/backlog open-pr #12 #14
```
  —— 指定需求（issue）列表

Interview

引导对话

Ask with structured multiple-choice questions (AskUserQuestion in Claude Code; plain questions elsewhere). One round per step — this is a router, not a grilling.

使用结构化选择题提问（在Claude Code中使用AskUserQuestion；其他环境下使用普通问题）。每一步一轮提问——这是一个路由工具，而非盘问。

Q1 — Goal

问题1 —— 目标

What should this session drive toward?

merge-pr — take PRs (and optionally fresh issues) all the way to merged, releases included.
open-pr — implement issues and stop at merge-ready open PRs; the human merges.

本次会话的目标是什么？

merge-pr —— 将PR（可选择包含新需求）全程推进至合并完成，包括发布环节。
open-pr —— 实现需求并在PR处于可合并状态时停止；由人工完成合并操作。

Q2 — branch on the answer

问题2 —— 根据回答分支处理

If merge-pr:

What's in scope?

All open PRs in the repo (default).
Specific PRs — take the list from args or ask.
Issues first, then all PRs — run
```
implement-issues
```
on issues without PRs, then babysit everything open.

If open-pr:

Which issues?

All open issues without a PR (default).
Specific issues — take the list from args or ask.

Do not ask about repo (use the current checkout), sub-agents, lint, or release handling — those are fixed by standing policy below.

若选择merge-pr：

本次处理的范围是什么？

所有已开放的PR（默认选项）。
指定PR —— 从参数中获取列表或询问用户。
先处理需求，再处理所有PR —— 对未关联PR的需求执行
```
implement-issues
```
，然后跟进所有已开放的PR。

若选择open-pr：

处理哪些需求？

所有未关联PR的开放需求（默认选项）。
指定需求 —— 从参数中获取列表或询问用户。

无需询问仓库信息（使用当前检出的仓库）、子Agent、代码检查（lint）或发布处理——这些均由下方的既定策略统一规定。

Q3 — Plan confirmation (deliberate, keep it)

问题3 —— 计划确认（务必保留此步骤）

The interview scopes the session; it does not replace the composed skills' own confirm steps. After triage, present the concrete plan — the issue/PR set, any surprises found (stale issues, no-PR-shaped work, orphaned branches), and any decision the issues themselves reserve for the owner — and confirm before spawning lanes. The owner wants to be in the loop on judgment calls the workflow would otherwise assume; never trade this checkpoint away for fewer clicks.

引导对话用于确定会话范围；不能替代组合Skill自身的确认步骤。完成分类后，展示具体计划——需求/PR集合、发现的异常情况（如过期需求、无对应PR的工作、孤立分支）以及需求本身留给所有者的决策事项——并在启动任务流前确认。所有者希望知晓工作流默认处理之外的判断决策；切勿为了减少操作步骤而省略此检查点。

Routing

路由规则

merge-pr → for the issues-first variant, run the
```
implement-issues
```
skill to open PRs, then run the
```
babysit-pr
```
skill with
```
--merge
```
across the in-scope PRs (one babysitter for all of them, per that skill's guidance). Otherwise go straight to
```
babysit-pr --merge
```
.
open-pr → run the
```
implement-issues
```
skill, then run the
```
babysit-pr
```
skill without
```
--merge
```
across the resulting PRs (one babysitter for all of them, per that skill's guidance) until Phase 5 exit conditions hold (threads resolved, checks green). Report PR URLs and stop — never merge in this mode.

Read and follow the composed skills at dispatch time; do not restate their workflows here.

merge-pr → 若为先处理需求的变体，先运行
```
implement-issues
```
Skill以创建PR，然后对范围内的所有PR执行
```
babysit-pr
```
Skill并添加
```
--merge
```
参数（根据该Skill的指导，为所有PR分配一个跟进者）。否则直接执行
```
babysit-pr --merge
```
。
open-pr → 运行
```
implement-issues
```
Skill，然后对生成的PR执行
```
babysit-pr
```
Skill不添加
```
--merge
```
参数（根据该Skill的指导，为所有PR分配一个跟进者），直至满足阶段5的退出条件（线程已解决、检查通过）。报告PR链接后停止——此模式下绝不执行合并操作。

调度时请阅读并遵循组合Skill的要求；无需在此重述它们的工作流。

Standing policy (applies to every route)

既定策略（适用于所有路由）

Red
main
is P0. If
```
main
```
is or goes red at any point: pause the current lane, file an issue (per the
```
issue
```
skill), fix it on a branch (per the
```
pr
```
skill), babysit that PR first, then resume.
Assess before amplifying. When babysitting PRs you did not implement in this session, review the implementation on its merits; where you disagree, fix or push back on the PR rather than shepherding it through unchanged.
CodeRabbit rate limits do not block exit — now the
```
babysit-pr
```
Step E default; no override needed.
Releases: follow the composed skills' release handling (1 PR = 1 release where that is the repo convention).
Sub-agents: run lanes and babysitters as background sub-agents so the main thread stays free, where the harness supports it.

主线分支（main）异常为最高优先级（P0）。若主线分支当前或变为异常状态：暂停当前任务流，按照
```
issue
```
Skill的要求创建需求，在分支上修复问题（按照
```
pr
```
Skill的要求），优先跟进该PR，然后恢复原任务流。
先评估再推进。当跟进并非本次会话中实现的PR时，根据实际情况评估实现内容；若存在不同意见，应修复或反馈PR问题，而非直接原样推进。
CodeRabbit速率限制不阻碍退出 —— 现为
```
babysit-pr
```
步骤E的默认设置；无需覆盖。
发布：遵循组合Skill的发布处理规则（若仓库惯例为1个PR对应1次发布，则按此执行）。
子Agent：在工具支持的情况下，将任务流和跟进者作为后台子Agent运行，以保持主线程空闲。

Final report

最终报告

Whatever the route, end with: PRs opened, PRs merged (or n/a), releases merged, blocked lanes with reasons, and any pending human gates.

无论选择哪种路由，最终报告需包含：已创建的PR、已合并的PR（或无）、已完成的发布、被阻塞的任务流及原因，以及任何待人工处理的环节。