Back to Details

implement-issue

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Implement Issue

实现Issue

Follow this strict mattpocock workflow to implement a GitHub issue end-to-end.
严格遵循此mattpocock工作流，端到端实现GitHub Issue。

Quick start

快速开始

When the user says "Implement issue #42" or asks you to take ownership of an issue, execute the workflow below against that issue.
当用户说“实现Issue #42”或要求您承接某个Issue时，针对该Issue执行以下工作流。

Workflows

工作流

1. Gather the Contract

1. 收集合同

  • Fetch the issue from the issue tracker.
  • Read both the issue body and the "Agent Brief" in the comments.
  • The Agent Brief is your absolute contract. Pay special attention to the "Out of scope" section—do absolutely NO gold-plating outside of these boundaries.
  • 从问题跟踪器中获取Issue。
  • 阅读Issue正文和评论中的“Agent Brief”。
  • Agent Brief是您的绝对合同。特别注意“超出范围”部分——绝对不要在这些边界之外进行额外功能添加。

2. Test-Driven Implementation

2. 测试驱动开发实现

  • Use the 
    /idd:tdd
    skill to drive the implementation.
  • First, write failing tests against the interfaces specified in the brief. Ensure you are testing behaviors at the boundaries (e.g. Services, Ports), not internal implementation details.
  • Run the tests to see them fail.
  • Implement the requested features until all tests pass.
  • 使用
    /idd:tdd
    技能驱动实现过程。
  • 首先，针对Brief中指定的接口编写失败测试。确保您测试的是边界处的行为（例如服务、端口），而非内部实现细节。
  • 运行测试以确认它们失败。
  • 实现所需功能，直到所有测试通过。

3. Verify Acceptance Criteria

3. 验证验收标准

  • Before committing, double-check that every single item in the Agent Brief's "Acceptance criteria" list is fully satisfied.
  • Run all project tests and linters to ensure nothing else was broken.
Stop here. The caller (e.g. 
parallel-issue-runner
) is responsible for committing, pushing, commenting, and closing the issue.
  • 提交前，仔细检查Agent Brief的“验收标准”列表中的每一项是否都完全满足。
  • 运行所有项目测试和代码检查工具，确保没有破坏其他功能。
到此为止。调用方（例如
parallel-issue-runner
）负责提交、推送、评论和关闭Issue。