| name | to-spec |
| description | Turn the current conversation into a spec and publish it to the project issue tracker — no interview, just synthesis of what you've already discussed. |
| 触发词 | 将当前对话转化为规格说明并发布到项目 Issue 跟踪器——无需提问，只需综合已讨论的内容。 |
| disable-model-invocation | true |
Turn the current conversation into a spec and publish it to the project issue tracker — no interview, just synthesis of what you've already discussed.
This skill takes the current conversation context and codebase understanding and produces a spec (you may know this document as a PRD). Do NOT interview the user — just synthesize what you already know.
本技能将当前对话上下文和代码库理解综合为一份规格说明（你可能知道这种文档叫 PRD）。不要向用户提问——只需综合已有信息即可。
The issue tracker and triage label vocabulary should have been provided to you — run /setup-matt-pocock-skills if not.
Issue 跟踪器和分诊标签词汇应已提供给你——如果尚未提供，运行 /setup-matt-pocock-skills。
1. Explore the repo to understand the current state of the codebase, if you haven't already. Use the project's domain glossary vocabulary throughout the spec, and respect any ADRs in the area you're touching.
1. 如果你尚未熟悉代码库，先探索仓库以了解其当前状态。在整个规格说明中使用项目的领域术语词汇，并尊重你涉及范围内的任何 ADR。
2. Sketch out the seams at which you're going to test the feature. Existing seams should be preferred to new ones. Use the highest seam possible. If new seams are needed, propose them at the highest point you can. The fewer seams across the codebase, the better — the ideal number is one.
2. 勾勒出你将用于测试该功能的接缝。优先使用现有接缝而非新建接缝。尽可能使用最高层接缝。如需新接缝，尽可能在最上层提出。代码库中的接缝越少越好——理想数量是一个。
Check with the user that these seams match their expectations.
与用户确认这些接缝是否符合其预期。
3. Write the spec using the template below, then publish it to the project issue tracker. Apply the ready-for-agent triage label — no need for additional triage.
3. 使用下方模板编写规格说明，然后发布到项目 Issue 跟踪器。应用 ready-for-agent 分诊标签——无需额外分诊。
<spec-template>
## Problem Statement
The problem that the user is facing, from the user's perspective.
## Solution
The solution to the problem, from the user's perspective.
## User Stories
A LONG, numbered list of user stories. Each user story should be in the format of:
1. As an <actor>, I want a <feature>, so that <benefit>
<user-story-example>
1. As a mobile bank customer, I want to see balance on my accounts, so that I can make better informed decisions about my spending
</user-story-example>
This list of user stories should be extremely extensive and cover all aspects of the feature.
## Implementation Decisions
A list of implementation decisions that were made. This can include:
- The modules that will be built/modified
- The interfaces of those modules that will be modified
- Technical clarifications from the developer
- Architectural decisions
- Schema changes
- API contracts
- Specific interactions
Do NOT include specific file paths or code snippets. They may end up being outdated very quickly.
Exception: if a prototype produced a snippet that encodes a decision more precisely than prose can (state machine, reducer, schema, type shape), inline it within the relevant decision and note briefly that it came from a prototype. Trim to the decision-rich parts — not a working demo, just the important bits.
## Testing Decisions
A list of testing decisions that were made. Include:
- A description of what makes a good test (only test external behavior, not implementation details)
- Which modules will be tested
- Prior art for the tests (i.e. similar types of tests in the codebase)
## Out of Scope
A description of the things that are out of scope for this spec.
## Further Notes
Any further notes about the feature.</spec-template><spec-template>
## Problem Statement（问题陈述）
用户面临的问题，从用户视角出发。
## Solution（解决方案）
问题的解决方案，从用户视角出发。
## User Stories（用户故事）
一份编号的长列表，列出用户故事。每个用户故事应采用以下格式：
1. 作为<角色>，我想要<功能>，以便<收益>
<user-story-example>
1. As a mobile bank customer, I want to see balance on my accounts, so that I can make better informed decisions about my spending
</user-story-example>
这份用户故事列表应极为详实，涵盖功能的所有方面。
## Implementation Decisions（实现决策）
已做出的实现决策列表。可包括：
- 将要构建/修改的模块
- 将要修改的那些模块的接口
- 来自开发者的技术澄清
- 架构决策
- Schema 变更
- API 契约
- 特定交互
不要包含具体的文件路径或代码片段。它们可能很快就会过时。
例外：如果原型产生了比文字更精确地编码决策的片段（状态机、reducer、schema、类型形状），将其内联在相关决策中，并简要注明来自原型。裁剪到决策丰富的部分——不是工作演示，只是重要的内容。
## Testing Decisions（测试决策）
已做出的测试决策列表。包括：
- 什么是好测试的描述（只测试外部行为，不测实现细节）
- 哪些模块将被测试
- 测试的既有先例（即代码库中类似类型的测试）
## Out of Scope（超出范围）
对本规格说明超出范围的描述。
## Further Notes（补充说明）
关于该功能的任何补充说明。</spec-template>