Individual skill
to-spec
把当前对话转成 spec 并发布到项目 issue tracker:不做访谈,只综合已经讨论的内容。
skills/engineering/to-spec/SKILL.md
Source commit 5b57718666917f8a6a0ff3066ae8d5ec386baef4
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Network or broad shell
- Last checked
- Nov 9, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 5,691
- Repository last updated
- Nov 10, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- ai-agent Repository topic
- chinese Repository topic
- developer-skills Repository topic
- productivity Repository topic
- prompt-engineering Repository topic
- skills Repository topic
- translation Repository topic
- vibe-coding Repository topic
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 2,679 bytesagents/openai.yamlasset · 124 bytes
Read excerpt
这个 skill 使用当前 conversation context 和 codebase understanding 产出 spec。**不要**访谈用户,只综合你已经知道的内容。
Issue tracker 和 triage label vocabulary 应该已经提供给你;如果没有,请让用户运行 `/setup-matt-pocock-skills`。
## 流程
1. 如果还没有探索 repo,先探索它以理解 codebase 当前状态。在 spec 中始终使用项目 domain glossary vocabulary,并遵守相关 ADRs。
2. 草拟你准备在哪些 seams 上测试这个 feature。优先使用现有 seams,而不是新增 seams。使用尽可能高层的 seam。如果确实需要新增 seams,尽可能在最高层提出。
Seams 越少越好,理想数量是一个。与用户确认这些 seams 是否符合预期。
3. 使用下面模板写 spec,并发布到项目 issue tracker。应用 `ready-for-agent` triage label;不需要额外 triage。