免费在 GitHub 公开中文介绍

implement-spec

读取规格说明和相关工单的依赖关系，安排多个代理推进实现。经过测试、代码审查和问题修正后，将成果汇总到一个集成分支，并完成工单处理。

原文查看原文说明

Implement the result of /to-spec and /to-tickets in code.

mattpocock/skills

AI 评分70分/ 100 查看安装方法

适用场景

实现分散在多个工单中的需求
并行实现相互独立的任务
将成果汇总到集成分支
审查代码并完成工单处理

中文介绍

功能

implement-spec依据规格说明和相关工单，将整个实现汇总到一个集成分支。它读取工单之间的依赖关系，把可以开始的工作分配给多个代理。各代理在独立的工作目录和分支中实现任务，完成的成果依次集成。最后进行代码审查、修正发现的问题，并完成工单处理。

适用场景

适用于实现拆分为多个工单的功能，或希望并行推进相互独立的工作。各代理通过共享规格说明、调研笔记和提交引用来协调任务。

使用示例

“请实现通过/to-spec和/to-tickets创建的规格与工单。”
“请检查依赖关系，并行实现可独立推进的任务，再汇总到集成分支。”

注意事项

需要规格说明、相关工单，以及问题跟踪工具的信息。如果尚未配置问题跟踪工具，会提示运行/setup-matt-pocock-skills。实现时调用tdd，最终检查时调用code-review。如果工作流程通过PR完成任务，会创建草稿PR，并在工作完成后将其改为可供审查的状态。

本介绍由 AI（OpenAI Codex）根据公开的 SKILL.md 撰写。准确的规格请查看下方原文。

客观评估

AI 仅根据 SKILL.md 的内容，从 4 个方面进行了评估。星标数和热度不计入评估。

指令清晰度能否看出何时使用、做什么: A良好明确说明实现规格与工单、汇总到集成分支并完成工单处理的目标。
步骤具体性步骤、输入输出和示例是否具体: A良好步骤涵盖依赖分析、独立实现、集成、审查和工作树清理。
安全性发送数据、删除文件、执行命令等是否有说明: C需确认指示重置分支、合并、更新PR和清理工作树，但没有确认步骤。
安装难易度所需工具和 API 密钥是否少且有说明: B部分不足需要问题跟踪配置、tdd和code-review，但未包含各项安装配置步骤。

总分按每项 A=25 分、B=15 分、C=5 分相加。由 AI（OpenAI Codex）于 2026年10月19日评估。仅供参考，安装前请同时查看原文。

如果您认为评估有误，请申请复核

包含的文件（2）

SKILL.md2.7 KB
agents/openai.yaml168 B

SKILL.md（原文）

安装前可以查看交给 AI 代理的指令内容。

You have been provided a spec. This spec should have tickets associated with it, describing how to implement the spec.

The issue tracker should have been provided to you. If not, tell the user to run /setup-matt-pocock-skills.

The goal is the entire spec implemented on a single integration branch, with every ticket resolved the way the issue tracker closes work.

The tickets are not a list of steps. They are a task graph with blocking relationships between them. This means there is always a frontier of tickets which are ready to be grabbed.

Communication to and from subagents should be sparse. Communicate primarily through context pointers: to the spec, tickets, research notes, and previous commits. Don't duplicate information already available via pointers.

Implementer subagents should be run in the background where possible for maximum concurrency.

Steps

Read the spec and tickets to understand the task graph.
(optional) Use an exploration subagent to conduct any exploration required by the tickets - relevant codebase files or external documentation. Ensure the exploration subagent can save files - it should save its markdown notes in a directory outside the repo, accessible by all future subagents. This lets implementer subagents focus on implementation rather than exploration.
Create the integration branch. If the issue tracker closes work through PRs, or the user asks for one, open a draft PR after the first merge in step 5 (a branch with no commits ahead of main can't open one), marked as closing the spec and tickets.
Use implementer subagents to implement each ticket, each in its own worktree on its own branch. Each implementer subagent:
- confirms its worktree is based on the integration branch before starting, and resets onto it if not;
- calls the Skill tool with tdd to build the ticket;
- merges the integration branch tip into its own branch before reporting done
Once an implementer subagent completes, merge its work to the integration branch with a merger subagent.
If this changes the frontier of available tickets, kick off more implementer subagents to work on the new tickets. This allows for maximum concurrency.
Once all tickets are complete, call the Skill tool with code-review on the integration branch. Fix all issues raised by the code review in a single implementer subagent.
If a draft PR exists, mark it ready for review. Otherwise, resolve each ticket the way the issue tracker closes work, and report the integration branch.
Clean up all implementer subagent worktrees.

评价

还没有评价。欢迎分享你的使用感受。

无需登录即可发表。欢迎分享使用感受、提问，或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

同一仓库的技能