develop-issue

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Develop Issue

开发Issue

Quick Start

快速开始

Invoke with exactly one same-repository GitHub issue reference:

text

/develop-issue #123
/develop-issue https://github.com/<owner>/<repo>/issues/123

This skill coordinates existing workflow skills. It does not replace their contracts, loosen their guardrails, or merge pull requests.

调用时需传入单个同一仓库的GitHub issue引用：

text

/develop-issue #123
/develop-issue https://github.com/<owner>/<repo>/issues/123

该Skill用于协调现有工作流Skill，不会替代它们的约定、放宽限制或合并拉取请求（PR）。

Required Child Skills

必需的子Skill

Before branch setup or implementation, confirm these installed skills are available in the agent environment:

```
new-branch
```
```
tdd
```
```
diagnose
```
```
review-code
```
```
finish-pr
```

If any are missing, halt before implementation. Report the missing skill names and install guidance:

npm_config_ignore_scripts=true npx skills@latest add patinaproject/skills --skill new-branch --skill review-code --skill finish-pr -y
npm_config_ignore_scripts=true npx skills@latest add mattpocock/skills@tdd -y
npm_config_ignore_scripts=true npx skills@latest add mattpocock/skills@diagnose -y

The

tdd

diagnose

write-a-skill

zoom-out

, and

prototype

install hints intentionally track their source catalog's default branch. Consumers who need a frozen install can add

#<git-ref>

to those sources.

在分支创建或实现之前，确认代理环境中已安装以下Skill：

```
new-branch
```
```
tdd
```
```
diagnose
```
```
review-code
```
```
finish-pr
```

如果缺少任何一个，在开始实现前停止操作，并报告缺失的Skill名称及安装指引：

npm_config_ignore_scripts=true npx skills@latest add patinaproject/skills --skill new-branch --skill review-code --skill finish-pr -y
npm_config_ignore_scripts=true npx skills@latest add mattpocock/skills@tdd -y
npm_config_ignore_scripts=true npx skills@latest add mattpocock/skills@diagnose -y

tdd

、

diagnose

、

write-a-skill

、

zoom-out

和

prototype

的安装指引默认跟踪其源目录的默认分支。需要固定版本安装的用户可在源地址后添加

#<git-ref>

。

Conditional Routes

条件路由

Conditional routes are not blanket prerequisites. Check that the named skill is available only when the issue triggers that route; halt with the missing skill name and install guidance only for a triggered missing route.

Install guidance for triggered conditional routes:

npm_config_ignore_scripts=true npx skills@latest add mattpocock/skills@write-a-skill -y
npm_config_ignore_scripts=true npx skills@latest add mattpocock/skills@zoom-out -y
npm_config_ignore_scripts=true npx skills@latest add mattpocock/skills@prototype -y

Route through
```
write-a-skill
```
when the issue changes an installable skill package surface: skill entry instructions, frontmatter or description, workflow contract text, examples, reference material, or bundled helper scripts. For skill-package changes that include executable helper scripts, run
```
write-a-skill
```
before
```
tdd
```
, then use
```
tdd
```
for executable behavior.
Use
```
zoom-out
```
for ad-hoc, read-only discovery when the agent cannot yet explain the relevant modules, callers, and domain vocabulary. It may run in a background explorer when the host supports that, but the main workflow must consume the result before choosing an implementation route.
Use
```
prototype
```
only when the issue explicitly asks for throwaway exploration, state-model sanity checks, UI direction exploration, or equivalent prototype work. Delete or absorb prototype output before local review unless the issue explicitly asks to commit prototype artifacts.

Do not add normal

/develop-issue

routes for upstream planning, triage, architecture review, handoff, or conversation-mode skills unless the issue explicitly asks for them.

条件路由并非通用前置要求。仅当issue触发对应路由时，才检查该Skill是否可用；仅当触发的路由对应的Skill缺失时，才停止操作并报告缺失的Skill名称及安装指引。

触发条件路由时的安装指引：

npm_config_ignore_scripts=true npx skills@latest add mattpocock/skills@write-a-skill -y
npm_config_ignore_scripts=true npx skills@latest add mattpocock/skills@zoom-out -y
npm_config_ignore_scripts=true npx skills@latest add mattpocock/skills@prototype -y

当issue涉及可安装Skill包的表面内容变更时（如Skill入口说明、前置内容或描述、工作流约定文本、示例、参考资料或捆绑的辅助脚本），路由至
```
write-a-skill
```
。若Skill包变更包含可执行辅助脚本，需先运行
```
write-a-skill
```
，再使用
```
tdd
```
处理可执行行为。
当代理无法解释相关模块、调用方和领域术语时，使用
```
zoom-out
```
进行临时的只读探索。若宿主支持，可在后台运行探索，但主工作流必须在选择实现路径前获取探索结果。
仅当issue明确要求进行一次性探索、状态模型合理性检查、UI方向探索或类似原型工作时，才使用
```
prototype
```
。除非issue明确要求提交原型产物，否则在本地评审前需删除或整合原型输出。

除非issue明确要求，否则不要为上游规划、分类、架构评审、交接或对话模式Skill添加常规

/develop-issue

路由。

Input Contract

输入约定

Accept one bare issue number,
```
#<number>
```
, or same-repository GitHub issue URL.
Reject missing issue references.
Reject multiple issue references.
Reject cross-repository issue URLs.
Resolve the issue through the current working directory's default
```
gh
```
repository.
Treat the issue as prior approval for implementation only when acceptance criteria, scope, repository rules, and design decisions are actionable.

Pause for a human when the issue lacks actionable acceptance criteria, conflicts with repository rules, requires a design decision, depends on external access, or otherwise needs judgment not recorded in the issue.

接受单个裸issue编号（
```
#<number>
```
）或同一仓库的GitHub issue URL。
拒绝缺失issue引用的请求。
拒绝多个issue引用的请求。
拒绝跨仓库的issue URL。
通过当前工作目录的默认
```
gh
```
仓库解析issue。
仅当issue包含可执行的验收标准、范围、仓库规则和设计决策时，才将其视为已获批准可进行实现。

当issue缺少可执行的验收标准、与仓库规则冲突、需要设计决策、依赖外部访问或需要issue中未记录的判断时，暂停操作并等待人工介入。

Workflow

工作流

Read
```
AGENTS.md
```
and
```
CLAUDE.md
```
if present, plus any docs they import.
Validate the single same-repository issue reference and required child skills.
Delegate branch setup to
```
new-branch
```
; inherit every halt.
Apply any triggered conditional route:
- Route installable skill package surface changes through
```
write-a-skill
```
  .
- Use
```
zoom-out
```
  before implementation routing when discovery is needed.
- Use
```
prototype
```
  only for explicit throwaway exploration requests.
Implement one behavior at a time through
```
tdd
```
;
```
tdd
```
stays in the main thread so the issue controller keeps ownership of implementation decisions.
Route to
```
diagnose
```
when root cause is unclear, reproduction is missing, behavior is flaky, or performance has regressed.
Run repository-documented verification before local review.
Check for reviewable local changes after verification: committed branch diff from the default-branch merge base, staged changes, unstaged changes, or untracked files.
When reviewable changes exist, invoke
```
review-code
```
and inherit its full contract.
```
review-code
```
owns fresh reviewer dispatch, isolation requirements, read-only boundary, cleanup, and halt reporting. Explicit use of
```
develop-issue
```
is sufficient approval for this required local review gate: dispatch the fresh read-only reviewer without asking for another user confirmation. Preserve the
```
review-code
```
boundary exactly: no same-thread fallback and no file edits, staging, commits, pushes, PR comments, review-thread mutation, or other worktree mutation. Halt if fresh reviewer dispatch is unavailable or if
```
review-code
```
reports a halt condition. When no reviewable changes exist, skip
```
review-code
```
and report that no local changes required review.
Triage every local review finding with the router below.
Repeat implementation, verification, reviewable-change detection, and
```
review-code
```
until no actionable local findings remain or a human-owned blocker appears.
Delegate final publishing and PR readiness to
```
finish-pr
```
only after local verification and
```
review-code
```
are clean, skipped because no reviewable local changes exist, or every local finding has a recorded
```
ready-for-agent
```
,
```
ready-for-human
```
, or
```
wontfix
```
disposition; inherit every halt. Never merge the pull request.

读取
```
AGENTS.md
```
和
```
CLAUDE.md
```
（如果存在）及其导入的所有文档。
验证单个同一仓库的issue引用及必需的子Skill。
将分支创建任务委托给
```
new-branch
```
；继承所有停止条件。
应用触发的条件路由：
- 可安装Skill包表面内容变更路由至
```
write-a-skill
```
  。
- 当需要探索时，在实现路由前使用
```
zoom-out
```
  。
- 仅针对明确的一次性探索请求使用
```
prototype
```
  。
通过
```
tdd
```
逐个实现功能；
```
tdd
```
运行在主线程中，以便issue控制器保持对实现决策的所有权。
当根本原因不明确、缺少复现步骤、行为不稳定或性能退化时，路由至
```
diagnose
```
。
在本地评审前运行仓库文档中规定的验证步骤。
验证后检查是否存在可评审的本地变更：从默认分支合并基准开始的已提交分支差异、暂存变更、未暂存变更或未跟踪文件。
若存在可评审的变更，调用
```
review-code
```
并遵循其完整约定。
```
review-code
```
负责新评审者调度、隔离要求、只读边界、清理和停止状态报告。显式使用
```
develop-issue
```
即视为已批准该必需的本地评审环节：无需再次请求用户确认，直接调度新的只读评审者。严格遵守
```
review-code
```
的边界：不使用同线程回退，不进行文件编辑、暂存、提交、推送、PR评论、评审线程修改或其他工作区变更。若无法调度新评审者或
```
review-code
```
报告停止条件，暂停操作。若无可评审变更，跳过
```
review-code
```
并报告无需评审本地变更。
使用下方的路由规则对每个本地评审发现进行分类。
重复实现、验证、可评审变更检测和
```
review-code
```
流程，直到没有可处理的本地发现或出现人工阻塞项。
仅当本地验证和
```
review-code
```
无问题、因无可评审本地变更而跳过，或所有本地发现均已标记为
```
ready-for-agent
```
、
```
ready-for-human
```
或
```
wontfix
```
状态后，才将最终发布和PR准备任务委托给
```
finish-pr
```
；继承所有停止条件。切勿合并拉取请求。

Review Finding Router

评审发现路由规则

Classify findings into exactly one of these outcomes:

Outcome	Use When	Next Action
`ready-for-agent`	The expected behavior is clear or evidence can be gathered locally	Route clear behavior changes to `tdd` ; route unclear root cause, missing reproduction, flaky behavior, or performance regression to `diagnose`
`ready-for-human`	The finding needs judgment, external access, manual testing, design input, missing information, changed scope, product decisions, permissions, conflicting direction, or valid work outside the issue	Stop the loop and report the blocker with evidence checked
`wontfix`	The finding is stale, incorrect, conflicts with repository rules, or is intentionally rejected	Explain politely in the report; add concise code comments only when future reviewers would otherwise re-raise the same concern

There is no

needs-info

state in v1. Insufficient information maps to

ready-for-human

将发现精确分类为以下结果之一：

结果	使用场景	下一步操作
`ready-for-agent`	预期行为明确或可在本地收集证据	将明确的行为变更路由至 `tdd` ；将不明确的根本原因、缺少复现步骤、不稳定行为或性能退化路由至 `diagnose`
`ready-for-human`	发现需要人工判断、外部访问、手动测试、设计输入、缺失信息、范围变更、产品决策、权限、冲突指令或issue外的有效工作	停止循环并报告包含已核实证据的阻塞项
`wontfix`	发现已过时、不正确、与仓库规则冲突或被故意拒绝	在报告中礼貌解释；仅当未来评审者可能再次提出相同问题时，添加简洁的代码注释

v1版本中没有

needs-info

状态。信息不足归类为

ready-for-human

。

Final Report

最终报告

When the workflow stops, report:

Issue reference and URL
Branch name
Child skills invoked, with halt reason if any
Verification commands and results
Latest
```
review-code
```
result, or that it was skipped because no reviewable local changes existed
Human-owned blockers, if any
```
wontfix
```
explanations, if any
PR URL and readiness status, when
```
finish-pr
```
runs

当工作流停止时，报告以下内容：

issue引用及URL
分支名称
调用的子Skill（若有停止原因需一并说明）
验证命令及结果
最新的
```
review-code
```
结果，或因无可评审本地变更而跳过的说明
人工阻塞项（若有）
```
wontfix
```
的解释（若有）
当
```
finish-pr
```
运行时，PR的URL及就绪状态